Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: NextJS local dev environment breaks in edge runtime #145

Open
matteobad opened this issue Feb 14, 2024 · 7 comments
Open

Bug: NextJS local dev environment breaks in edge runtime #145

matteobad opened this issue Feb 14, 2024 · 7 comments
Assignees
Labels
🐛 bug Something isn't working 🚀 Good first issue Good for newcomers

Comments

@matteobad
Copy link
Collaborator

matteobad commented Feb 14, 2024

Describe the bug

NextJS local dev environment breaks in edge runtime
Ref: vercel/next.js#52176

We should remove/comment out all of the export const runtime = "edge" from pages

Steps to reproduce

  1. pnpm run dev:web
  2. Navigate any edge runtime page
  3. See errors in console

Additional context (Is this in dev or production?)

Windows local dev server

@matteobad matteobad added 🐛 bug Something isn't working 👀 Exploration Pending labels Feb 14, 2024
@Codehagen Codehagen added 🚀 Good first issue Good for newcomers 🐛 bug Something isn't working and removed 🐛 bug Something isn't working 👀 Exploration Pending labels Feb 14, 2024
@kennysliding
Copy link

Hello! I'm excited by what you guys are building and would love to contribute to the project, mind if I give this issue a go? Thanks and appreciate the great work!

@Codehagen
Copy link
Member

Hello @kennysliding - Assigning you the issue. @matteobad can test it after 👏

@Codehagen
Copy link
Member

Did you get a chance to look at it @kennysliding ?

@kennysliding
Copy link

@meglerhagen Yea, spent a bit time navigating the set up and repo, will create a PR for the fix today

@michaelwschultz
Copy link

Any progress here or has this already been done and not closed @kennysliding?

@Codehagen
Copy link
Member

Hi @michaelwschultz - We found the issue i think @matteobad ?

@Amirthananth
Copy link
Contributor

Amirthananth commented May 4, 2024

@Codehagen Is this fixed as part of #147 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working 🚀 Good first issue Good for newcomers
Projects
Development

No branches or pull requests

5 participants