-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Switch to Turbopack #20126
Comments
https://turbo.build/pack/docs/features/frameworks#vue-and-svelte I think we would not consider until it supports Angular/React/Vue? |
We supported webpack so it was easier and consistent to maintain a single tooling. angular -> angular-cli (currently uses webpack) |
I agree with your recommendations @mshima. |
The commercial argument for turbopack seems awesome, I think that it needs some tryout at least. |
I agree with @mshima too we should always strive to use the default for each framework as it make it easier for existing to projects to migrate in, and though who want to leave to migrate out. |
Makes perfect sense to support the official tooling, I opened this issue because turbo seems to be an order of magnitude faster than vite and several faster than webpack. In this case, do we just wait for the people behind the frontend frameworks to make the switch themselves? Thank you. |
This issue is stale because it has been open for too long without any activity. |
Overview of the feature request
Consider using Turbopack instead of Webpack.
Link to the github repo: https://github.com/vercel/turbo
Motivation for or Use Case
Turbopack seems to be the natural successor of Webpack with a focus on extensibility and performance.
Webpack is famously known for being slow, something that Turbopack aims to fix.
Related issues or PR
The text was updated successfully, but these errors were encountered: