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

ReferenceError: regeneratorRuntime is not defined #23757

Closed
ajmeraaxesh opened this issue Apr 7, 2021 · 5 comments
Closed

ReferenceError: regeneratorRuntime is not defined #23757

ajmeraaxesh opened this issue Apr 7, 2021 · 5 comments
Labels
bug Issue was opened via the bug report template.

Comments

@ajmeraaxesh
Copy link

What version of Next.js are you using?

10.1.1

What version of Node.js are you using?

15.13.0

What browser are you using?

Chrome, Safari

What operating system are you using?

macOS

How are you deploying your application?

Vercel

Describe the Bug

09:29:21.810 > Build error occurred
09:29:21.812 ReferenceError: regeneratorRuntime is not defined
09:29:21.812 at create (/vercel/path0/node_modules/zustand/index.js:156:31)
09:29:21.812 at Object.Bl7J (/vercel/path0/.next/server/pages/index.js:648:50)
09:29:21.813 at webpack_require (/vercel/path0/.next/server/pages/index.js:23:31)
09:29:21.813 at Module.RXBc (/vercel/path0/.next/server/pages/index.js:1352:14)
09:29:21.813 at webpack_require (/vercel/path0/.next/server/pages/index.js:23:31)
09:29:21.813 at Object.9 (/vercel/path0/.next/server/pages/index.js:498:18)
09:29:21.813 at webpack_require (/vercel/path0/.next/server/pages/index.js:23:31)
09:29:21.814 at /vercel/path0/.next/server/pages/index.js:91:18
09:29:21.814 at Object. (/vercel/path0/.next/server/pages/index.js:94:10)
09:29:21.814 at Module._compile (internal/modules/cjs/loader.js:999:30) {
09:29:21.814 type: 'ReferenceError'
09:29:21.814 }

Expected Behavior

Should work without any issues

To Reproduce

Tryin to redeploy this on Vercel

I am completely clueless as to why this is happening on Vercel. The same commit I reverted back and try redeploying and I am seeing a similar error in Vercel. I have no babel.rc file.

09:29:21.810 > Build error occurred
09:29:21.812 ReferenceError: regeneratorRuntime is not defined
09:29:21.812 at create (/vercel/path0/node_modules/zustand/index.js:156:31)
09:29:21.812 at Object.Bl7J (/vercel/path0/.next/server/pages/index.js:648:50)
09:29:21.813 at webpack_require (/vercel/path0/.next/server/pages/index.js:23:31)
09:29:21.813 at Module.RXBc (/vercel/path0/.next/server/pages/index.js:1352:14)
09:29:21.813 at webpack_require (/vercel/path0/.next/server/pages/index.js:23:31)
09:29:21.813 at Object.9 (/vercel/path0/.next/server/pages/index.js:498:18)
09:29:21.813 at webpack_require (/vercel/path0/.next/server/pages/index.js:23:31)
09:29:21.814 at /vercel/path0/.next/server/pages/index.js:91:18
09:29:21.814 at Object. (/vercel/path0/.next/server/pages/index.js:94:10)
09:29:21.814 at Module._compile (internal/modules/cjs/loader.js:999:30) {
09:29:21.814 type: 'ReferenceError'
09:29:21.814 }

I am running locally and I am not seeing any error. I am not even sure if this is next's specific or how Vercel is deploying the builds

@ajmeraaxesh ajmeraaxesh added the bug Issue was opened via the bug report template. label Apr 7, 2021
@timneutkens
Copy link
Member

Duplicate of #23720

@timneutkens timneutkens marked this as a duplicate of #23720 Apr 7, 2021
@timneutkens
Copy link
Member

Please provide a complete reproduction on the other issue so that it can be investigated.

@ajmeraaxesh
Copy link
Author

I figured out, this is not an issue with the Nextjs library but more like Zustand lib. I reverted back to old version and it works again. Thanks for your response

@Yuripetusko
Copy link
Contributor

I figured out, this is not an issue with the Nextjs library but more like Zustand lib. I reverted back to old version and it works again. Thanks for your response

Got the same problem this morning by updating zutsang

@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 28, 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.
Projects
None yet
Development

No branches or pull requests

4 participants