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

Switch to Turbopack #20126

Closed
1 task done
vicpermir opened this issue Oct 26, 2022 · 7 comments
Closed
1 task done

Switch to Turbopack #20126

vicpermir opened this issue Oct 26, 2022 · 7 comments

Comments

@vicpermir
Copy link
Contributor

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
  • Checking this box is mandatory (this is just to show you read everything)
@zhx828
Copy link

zhx828 commented Oct 26, 2022

https://turbo.build/pack/docs/features/frameworks#vue-and-svelte I think we would not consider until it supports Angular/React/Vue?

@mshima
Copy link
Member

mshima commented Oct 26, 2022

We supported webpack so it was easier and consistent to maintain a single tooling.
But the situation has changed a lot, and we have very good alternatives.
IMO we should support the frontend official tooling now.

angular -> angular-cli (currently uses webpack)
vue -> vite
react -> was webpack through react-react-app, but I think it's somewhat just in maintenance now. developers seems to prefer vite.

@mraible
Copy link
Contributor

mraible commented Oct 26, 2022

I agree with your recommendations @mshima.

@Tcharl
Copy link
Contributor

Tcharl commented Oct 27, 2022

The commercial argument for turbopack seems awesome, I think that it needs some tryout at least.
They benchmarked it 1.5s startup compared to 7s on a vite build

@yelhouti
Copy link
Contributor

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.
Also it removes the maintenance/migration burden from the jhipster team

@vicpermir
Copy link
Contributor Author

vicpermir commented Oct 29, 2022

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.

Copy link
Contributor

github-actions bot commented Jan 6, 2024

This issue is stale because it has been open for too long without any activity.
Due to the moving nature of jhipster generated application, bugs can become invalid.
If this issue still applies please comment otherwise it will be closed in 7 days

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 13, 2024
@deepu105 deepu105 added this to the 8.2.0 milestone Mar 20, 2024
@Tcharl Tcharl mentioned this issue Apr 15, 2024
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants