-
Notifications
You must be signed in to change notification settings - Fork 27.6k
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: --turbo couldn't dayjs molude resolution within cal-heatmap library. #66826
Comments
The import unfortunately is too dynamic for turbopack to analyze, I'm not sure if this is something that can be fixed soon. |
@ForsakenHarmony Thanks for your hard work on this project! I noticed that the import is too dynamic for Turbopack to analyze. Hope this can be resolved. Keep up the great work! |
@sokra mentioned we'll likely have to support the |
Will be fixed with the next canary after turbopack is updated |
@ForsakenHarmony Thank you! |
…repo#8823) ### Description Adds support for `String.prototype.concat` which `dayjs` uses in an `import()` pattern. ### Testing Instructions Closes PACK-3118 Fixes #66826
…repo#8823) ### Description Adds support for `String.prototype.concat` which `dayjs` uses in an `import()` pattern. ### Testing Instructions Closes PACK-3118 Fixes #66826
…repo#8823) ### Description Adds support for `String.prototype.concat` which `dayjs` uses in an `import()` pattern. ### Testing Instructions Closes PACK-3118 Fixes #66826
…repo#8823) ### Description Adds support for `String.prototype.concat` which `dayjs` uses in an `import()` pattern. ### Testing Instructions Closes PACK-3118 Fixes #66826
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Link to the code that reproduces this issue
https://github.com/ryota-murakami/reproduction-turbopack-can-not-find-dayjs-local-module
To Reproduce
If you run with
pnpm dev
, the issue not happen.Current vs. Expected behavior
Expect Behavior(current 'next dev' behavior)
Show heatmap correctly.
Current Behavior
Build error turbo couldn't resolve
import("dayjs/locale/~
.Provide environment information
Operating System: Platform: darwin Arch: x64 Version: Darwin Kernel Version 23.5.0: Wed May 1 20:09:52 PDT 2024; root:xnu-10063.121.3~5/RELEASE_X86_64 Available memory (MB): 16384 Available CPU cores: 12 Binaries: Node: 22.2.0 npm: 10.7.0 Yarn: 1.22.22 pnpm: 9.3.0 Relevant Packages: next: 15.0.0-canary.28 // Latest available version is detected (15.0.0-canary.28). eslint-config-next: N/A react: 19.0.0-rc-6f23540c7d-20240528 react-dom: 19.0.0-rc-6f23540c7d-20240528 typescript: 5.3.3 Next.js Config: output: N/A
Which area(s) are affected? (Select all that apply)
Turbopack
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
I'd like to create UI similar to Github weed, so I tried Cal-Heatmap library in side project.
I use to
next dev --turbo
by default so I encountered this issue.I'm glad to this report will help Turbopack get a little closer to Webpack's drop in replacement. 😄
The text was updated successfully, but these errors were encountered: