-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
"Package path ./esm/config/templates/requestAsyncStorageShim.js is not exported from package" with latest Next.js canary releases #13925
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
Comments
I did find an older, resolved issue related to this: And the fix was here: |
Huh interestingly enough, our canary tests also caught this (internal link). I think the fix should address this but I wonder if there's more to the story. Looks like this went unnoticed previously. |
…#13928) Looks like we missed adding the `build` dir to the template path of `requestAsyncStorageShim` in the NextJS SDK when we changed the package-internal directory structure a while ago (IIRC this was pre-v8 but not sure actually) I'm a bit surprised that this works at all, given we use `exports` conditions and this is a path to a specific file not covered by any `exports` entry. But I guess webpack can handle this still. EDIT: Well turns out, this doesn't work. We'll need to add the `exports` entries. fixes #13925 closes #13926 closes #13927
Thank you! |
A PR closing this issue has just been released 🚀This issue was referenced by PR #13928, which was included in the 8.34.0 release. |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nextjs
SDK Version
8.33.1
Framework Version
Next.js 15.0.0-canary.181+
Link to Sentry event
No response
Reproduction Example/SDK Setup
Error when building:
Steps to Reproduce
Use
@sentry/nextjs
in a project running canary15.0.0-canary.181
or higher.Expected Result
Builds without errors.
Actual Result
Fails to build.
The text was updated successfully, but these errors were encountered: