search

jhipster / generator-jhipster

JHipster is a development platform to quickly generate, develop, & deploy modern web applications & microservice architectures.
https://www.jhipster.tech
Apache License 2.0
21.54k stars 4.02k forks source link

Switch to Turbopack #20126

Closed vicpermir closed 9 months ago

vicpermir commented 1 year ago
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
zhx828 commented 1 year ago

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

mshima commented 1 year ago

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 commented 1 year ago

I agree with your recommendations @mshima.

Tcharl commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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.

github-actions[bot] commented 9 months ago

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