Thanks to visit codestin.com
Credit goes to github.com

Skip to content

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

Open
ozanusug opened this issue Nov 1, 2024 · 14 comments
Open

Getting Turbopack fatal error while trying to start and run. #72196

ozanusug opened this issue Nov 1, 2024 · 14 comments
Labels
bug Issue was opened via the bug report template. linear: turbopack Confirmed issue that is tracked by the Turbopack team. Turbopack Related to Turbopack with Next.js.

Comments

@ozanusug
Copy link

ozanusug commented Nov 1, 2024

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

@ozanusug ozanusug added the bug Issue was opened via the bug report template. label Nov 1, 2024
@github-actions github-actions bot added the Turbopack Related to Turbopack with Next.js. label Nov 1, 2024
@AndreasWintherMoen
Copy link

Getting a very similar error with a nearly clean Next 15 project.

@timneutkens
Copy link
Member

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

@szwabodev
Copy link

Hello, I had exact same error when trying to run latest stable NextJS15 with tailwind. In my case the issue was related with the content config in tailwind.config.ts where one line was causing this fatal error:

export const content = [
    "./app/**/*.{js,ts,jsx,tsx,mdx}",
    "./pages/**/*.{js,ts,jsx,tsx,mdx}",
    "./components/**/*.{js,ts,jsx,tsx,mdx}",

    // The line below causes fatal error in turbo mode
    "./src/app/[locale]/**/*.{js,ts,jsx,tsx}",
];

Once I removed [locale] part from this content config, it built fine with turbo. Maybe it'll help some of you.

@tariqkb
Copy link

tariqkb commented Jan 29, 2025

I ran into this as well using and narrowed it down to an intercepted route on a dynamic param, i.e. (.)[dynamicParam] in case it's helpful to anyone

@frdepiaggio
Copy link

frdepiaggio commented Feb 6, 2025

Any updates on this? I ran into the same error when an intercepted route with dynamic param is defined -> (.)[id]

[UPDATE]

I solved the problem by avoiding creating folders with parentheses followed by brackets and navigating back using double dots. Going from this:

photo-feed/
β”œβ”€ @modal/
β”‚  β”œβ”€ (.)[id]/
β”‚  β”‚  └─ page.tsx
β”‚  └─ default.tsx
β”œβ”€ [id]/
β”‚  └─ page.tsx
β”œβ”€ layout.tsx
└─ page.tsx

to this:

photo-feed/
β”œβ”€ @modal/
β”‚  β”œβ”€ (..)photo-feed/
β”‚  β”‚  └─ [id]/
β”‚  β”‚     └─ page.tsx
β”‚  └─ default.tsx
β”œβ”€ [id]/
β”‚  └─ page.tsx
β”œβ”€ layout.tsx
└─ page.tsx

@cipriancaba
Copy link
Contributor

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

Panic: panicked at turbopack/crates/turbo-tasks-fs/src/glob.rs:180:25:
not yet implemented: glob char sequences are not implemented yet
Backtrace:    0: _napi_register_module_v1
   1: <unknown>
   2: _napi_register_module_v1
   3: _napi_register_module_v1
   4: _napi_register_module_v1
   5: _napi_register_module_v1
   6: _napi_register_module_v1
   7: _BrotliDecoderVersion
   8: _BrotliDecoderVersion
   9: _BrotliDecoderVersion
  10: _BrotliDecoderVersion

@roelvan
Copy link

roelvan commented Feb 10, 2025

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

Panic: panicked at turbopack/crates/turbo-tasks-fs/src/glob.rs:180:25:
not yet implemented: glob char sequences are not implemented yet
Backtrace:    0: _napi_register_module_v1
   1: <unknown>
   2: _napi_register_module_v1
   3: _napi_register_module_v1
   4: _napi_register_module_v1
   5: _napi_register_module_v1
   6: _napi_register_module_v1
   7: _BrotliDecoderVersion
   8: _BrotliDecoderVersion
   9: _BrotliDecoderVersion
  10: _BrotliDecoderVersion

I get the same "glob char" error after upgrading to tailwind v4 with npx @tailwindcss/upgrade@next.

@cipriancaba

This comment has been minimized.

@cipriancaba
Copy link
Contributor

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

Panic: panicked at turbopack/crates/turbo-tasks-fs/src/glob.rs:180:25:
not yet implemented: glob char sequences are not implemented yet
Backtrace:    0: _napi_register_module_v1
   1: <unknown>
   2: _napi_register_module_v1
   3: _napi_register_module_v1
   4: _napi_register_module_v1
   5: _napi_register_module_v1
   6: _napi_register_module_v1
   7: _BrotliDecoderVersion
   8: _BrotliDecoderVersion
   9: _BrotliDecoderVersion
  10: _BrotliDecoderVersion

I get the same "glob char" error after upgrading to tailwind v4 with npx @tailwindcss/upgrade@next.

We actually upgraded recently to tailwind v4 as well

@cipriancaba
Copy link
Contributor

So basically it works if we remove all the route intercepts, @ijjk

Pretty sure this should be an easy fix

Image

@SebassNoob
Copy link
Contributor

I ran into this issue when upgrading to tailwind 4.

I can reproduce a more minimal version here.
Here were the steps used to create this repro:

  1. npx create-next-app@latest with default options but no to tailwindcss.
  2. Follow tailwind v3 installation guide https://v3.tailwindcss.com/docs/guides/nextjs (steps 2-6)
  3. Update to v4 with @tailwindcss/upgrade@next
  4. In the app directory, create @test/(.)[test]/page.tsx and put a react component in it.
  5. Run the server npm run dev and open it in browser.
  6. This issue occurs.

I'm not sure if this is the most minimal reproduction that is possible, but is the closest match to my current situation.

@timdorr
Copy link

timdorr commented Feb 25, 2025

@SebassNoob I was able to fix this by installing the @tailwindcss/postcss package in my project.

@khuezy
Copy link
Contributor

khuezy commented Feb 27, 2025

@SebassNoob I was able to fix this by installing the @tailwindcss/postcss package in my project.

really? I'm still getting the glob char sequences are not implemented yet error.

@ek-kpr
Copy link

ek-kpr commented Mar 12, 2025

Same issue - when Upgrading to tailwind. We also use intercepted route, changing it to (..) did not work. However removing the route / folder.
Building is not affected, removing turbo flag from dev also makes "fixes" it.

@timneutkens timneutkens added the linear: turbopack Confirmed issue that is tracked by the Turbopack team. label Apr 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue was opened via the bug report template. linear: turbopack Confirmed issue that is tracked by the Turbopack team. Turbopack Related to Turbopack with Next.js.
Projects
None yet
Development

No branches or pull requests