Repository navigation
|
We’re excited to introduce Turbopack, the successor to Webpack:
This discussion is where you can provide feedback on the beta. View the documentation and see the currently supported features. |
Replies: 92 comments 107 replies
|
Running next dev --turbo quits instantly. package.json |
|
no tailwind :( |
|
We use Typescripts |
|
I'm getting warnings when using Turbopack that I don't think are valid. TypeScript shows a warning when attempting to use export type * from './events';Results in an It looks like TypeScript support for this syntax is not available yet, but may be coming soon: |
|
How do I debug using turbopack? I'm in the example and trying to add |
|
The I think this might have to do with the d15308b#diff-f925c8a54d0915699648170786b422f2132ff4751034dfe5c06afbcf565b94b0R92 One of my components is using a |
|
Turbopack failed for me without any message when the port was in use. Freeing the port and trying again worked fine. |
|
when i start development mode with turbo enabled ( (i am using the |
|
I tried using top level await and it doesn't work with turbopack - no surprise there; there are plenty of core features that have yet to be fleshed out. I just wanted to put my two cents in and say that I hope that there will be support for it since the top level await proposal is in stage 4 😬 |
update tailwind classname |
|
In the example from |
|
Keep getting this error when running 'next dev --turbo' after installing next v13 to my project: |
|
Thanks for all of your feedback so far! Now that we are in the beta phase for Some features are still not implemented, and we have been tracking them in this issue: vercel/next.js#49174 |
|
constantly fetching data while using clerk auth |
|
Fonts seem to default to lowest possible font weights. |
|
i have the same issue #2312 (comment) . i created a new nextjs project. it stucks at ready for more than an hour. i tried accessing localhost:3000/ on browser and got stuck at loading state |
TrailingSlash is working great on Next.js, however it's blocking the use of Turbo. There is no sign of it, is it coming someday or is it deprecated? It would greatly help me with future choices, thank you guys. |
|
I neglected to lock the conversation when I last provided an answer If you are experiencing issues with using Turbopack in Next.js, please open an issue with a reproduction on the Next.js repo. Thanks! |














Thanks for all of your feedback so far! Now that we are in the beta phase for
next dev --turbo, we would prefer people to open a GitHub issue with a reproduction if they are experiencing issues.Some features are still not implemented, and we have been tracking them in this issue: vercel/next.js#49174