Skip to content
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

Not compatible with Next Turbopack. -- not statically analyse-able #1071

Open
1 of 5 tasks
interactda opened this issue Dec 4, 2024 · 4 comments
Open
1 of 5 tasks
Labels
bug Something isn't working

Comments

@interactda
Copy link

interactda commented Dec 4, 2024

System Info

nextjs 15
transformer js 3.1.1
"dev": "next dev --turbopack",

Environment/Platform

  • Website/web-app
  • Browser extension
  • Server-side (e.g., Node.js, Deno, Bun)
  • Desktop app (e.g., Electron)
  • Other (e.g., VSCode extension)

Description

I am using turbopack for packaging my nextjs application for development, however it raised this not statically analyse-able problem. When I switch to webpack it is working okay. I am using nextjs 15 and ran the nextjs client demo. Not sure if current transformerjs support turbopack compilation or not.
WX20241204-181912@2x

Reproduction

change the "next dev" into "next dev --turbo" in the next-client demo package.json.

@interactda interactda added the bug Something isn't working label Dec 4, 2024
@bondia
Copy link

bondia commented Dec 5, 2024

Wow, just realised I might have the same issue.
Added a stackoverflow issue because I'm pretty much lost.
https://stackoverflow.com/q/79250686/2051149
Adding this just to show that @interactda might not be the only one having this issue.

@a1740942002
Copy link

a1740942002 commented Dec 6, 2024

I have the same issue.

"next": "^15.0.4",
"dev": "next dev --turbopack",

@xenova
Copy link
Collaborator

xenova commented Dec 6, 2024

This seems to be an issue with Next Turbopack and not Transformers.js. Could you open this issue in their repo?

@pearcircuitmike
Copy link

I also have this issue - is there a corresponding issue on the turbopack side? there is a next.js example but it doesn't appear to work if you're using turbopack

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants