-
Notifications
You must be signed in to change notification settings - Fork 28.3k
Getting Turbopack fatal error while trying to start and run. #72196
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
Getting a very similar error with a nearly clean Next 15 project. |
Hey! We'd love to investigate this but the shared codesandbox does not reproduce the issue, can you share a reproduction? I.e. when running your sandbox it works: https://codesandbox.io/p/devbox/hardcore-fermat-z4fttc?file=%2Fapp%2Fpage.tsx&workspaceId=062b139a-c054-40fe-bbf5-0210d48b9dd0 |
Hello, I had exact same error when trying to run latest stable NextJS15 with tailwind. In my case the issue was related with the
Once I removed |
I ran into this as well using and narrowed it down to an intercepted route on a dynamic param, i.e. |
Any updates on this? I ran into the same error when an intercepted route with dynamic param is defined -> [UPDATE] I solved the problem by avoiding creating folders with parentheses followed by brackets and navigating back using double dots. Going from this:
to this:
|
Seeing this in our monorepo too doesn't seem to be tailwind related, we do have a couple of intercept routes, too many to change, same panic
|
I get the same "glob char" error after upgrading to tailwind v4 with |
This comment has been minimized.
This comment has been minimized.
We actually upgraded recently to tailwind v4 as well |
So basically it works if we remove all the route intercepts, @ijjk Pretty sure this should be an easy fix |
I ran into this issue when upgrading to tailwind 4. I can reproduce a more minimal version here.
I'm not sure if this is the most minimal reproduction that is possible, but is the closest match to my current situation. |
@SebassNoob I was able to fix this by installing the |
really? I'm still getting the |
Same issue - when Upgrading to tailwind. We also use intercepted route, changing it to (..) did not work. However removing the route / folder. |
Link to the code that reproduces this issue
https://codesandbox.io/p/devbox/withered-https-go8s7s
To Reproduce
Panic: panicked at turbopack/crates/turbo-tasks-fs/src/glob.rs:179:25:
not yet implemented: glob char sequences are not implemented yet
Backtrace: 0:
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34: start_thread
35: clone
Current vs. Expected behavior
While i am trying to start next typescript project i am getting fatal turbopack error, FATAL: An unexpected Turbopack error occurred. Please report the content of log.
Provide environment information
Operating System: Platform: linux Arch: x64 Version: #1 SMP Debian 5.10.149-1 (2022-10-17) Available memory (MB): 24048 Available CPU cores: 10 Binaries: Node: 18.20.4 npm: 10.9.0 Yarn: N/A pnpm: N/A Relevant Packages: next: 15.0.2 // Latest available version is detected (15.0.2). eslint-config-next: 15.0.2 react: 19.0.0-rc-02c0e824-20241028 react-dom: 19.0.0-rc-02c0e824-20241028 typescript: 5.6.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
No response
The text was updated successfully, but these errors were encountered: