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

[regression]: __next_eval__ is not defined with next dev #31195

Closed
stefanprobst opened this issue Nov 9, 2021 · 1 comment · Fixed by #31219
Closed

[regression]: __next_eval__ is not defined with next dev #31195

stefanprobst opened this issue Nov 9, 2021 · 1 comment · Fixed by #31219
Labels
bug Issue was opened via the bug report template. Middleware Related to Next.js Middleware
Milestone

Comments

@stefanprobst
Copy link
Contributor

What version of Next.js are you using?

12.0.4-canary.0

What version of Node.js are you using?

16.13.0

What browser are you using?

firefox

What operating system are you using?

ubuntu

How are you deploying your application?

n/a

Describe the Bug

when running the following reproduction repo with yarn dev, i get a ReferenceError: __next_eval__ is not defined error.

reproduction repo: https://github.com/stefanprobst/issue-next-dynamic

notes:

  • works in 12.0.3, regression introduced in 12.0.4-canary.0
  • works with yarn build && yarn start, error only occurs with yarn dev

Expected Behavior

no error, like in 12.0.3.

To Reproduce

see link to repo above

@stefanprobst stefanprobst added the bug Issue was opened via the bug report template. label Nov 9, 2021
@timneutkens timneutkens added the Middleware Related to Next.js Middleware label Nov 9, 2021
@styfle styfle added this to the 12.0.4 milestone Nov 10, 2021
@styfle styfle linked a pull request Nov 10, 2021 that will close this issue
10 tasks
@kodiakhq kodiakhq bot closed this as completed in #31219 Nov 10, 2021
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template. Middleware Related to Next.js Middleware
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants