-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[turbopack] Invariant: AsyncLocalStorage accessed in runtime where it is not available #3319
Comments
I have the same issue |
I have the same issue, started facing it today so probably its a turbopack bug |
Same issue |
Yup, I got the same issue. |
Facing the same issue |
Same here |
same :( |
Same |
Same issue |
Same |
same |
1 similar comment
same |
Yep, still facing this issue too! |
Same issue |
Hi all, I'll be addressing this today. It's likely we'll need a new Next.js canary release in order for this to take effect. In the meantime, you should be able to |
Same issue |
vercel/next.js#44668 refactored Next's use of `AsyncLocalStorage`, and installs a "polyfill" of the API by patching the node import onto `globalThis.` Importantly, it's then used in the module scope during imports, so we need to install the polyfill early in the app rendering startup. Fixes #3319
change the 'next' to 13.1.0 in package.json and pnpm i |
I'm seeing it with 13.1.5 |
#44668 refactored Next's use of `AsyncLocalStorage`, and installs a "polyfill" of the API by patching the node import onto `globalThis.` Importantly, it's then used in the module scope during imports, so we need to install the polyfill early in the app rendering startup. Fixes vercel/turborepo#3319
#44668 refactored Next's use of `AsyncLocalStorage`, and installs a "polyfill" of the API by patching the node import onto `globalThis.` Importantly, it's then used in the module scope during imports, so we need to install the polyfill early in the app rendering startup. Fixes vercel/turborepo#3319
#44668 refactored Next's use of `AsyncLocalStorage`, and installs a "polyfill" of the API by patching the node import onto `globalThis.` Importantly, it's then used in the module scope during imports, so we need to install the polyfill early in the app rendering startup. Fixes vercel/turborepo#3319
#44668 refactored Next's use of `AsyncLocalStorage`, and installs a "polyfill" of the API by patching the node import onto `globalThis.` Importantly, it's then used in the module scope during imports, so we need to install the polyfill early in the app rendering startup. Fixes vercel/turborepo#3319
#44668 refactored Next's use of `AsyncLocalStorage`, and installs a "polyfill" of the API by patching the node import onto `globalThis.` Importantly, it's then used in the module scope during imports, so we need to install the polyfill early in the app rendering startup. Fixes vercel/turborepo#3319
What version of Turbopack are you using?
next 13.1.2
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Describe the Bug
Turbopack throws the runtime error
Invariant: AsyncLocalStorage accessed in runtime where it is not available
when attempting to start up a Next.js project withappDir: true
. Webpack works as expected.Expected Behavior
Turbopack should works as what Webpack does.
To Reproduce
appDir
enabled:pnpm dev --turbo
. It throws.Turbopack
Webpack
Reproduction Repo
No response
The text was updated successfully, but these errors were encountered: