-
-
Notifications
You must be signed in to change notification settings - Fork 246
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
Migrate to use Bun.js instead of Vite #1429
Comments
In the long term, this could be a good idea. Currently though, bun doesn't have an in-depth plugin system that support things like Vue. But Bun just uses esbuild behind the scenes, which Vite also uses. Plus, soon, Vite's going to use rolldown, and there will be speed improvements using native code. I have tried to keep Vite inside its own abstraction so we could hot swap it or provide alternative build solutions. But right now, I'm going to say no to this. |
OK. I wonder what's the best way to import the One caveat is Bun uses its own stuff instead of esbuild I think https://bun.sh/docs/bundler/vs-esbuild |
scripts not having its UI can hotswap without problem already |
Huh, you're right, I thought it just used esbuilt under the hood, but I guess I was wrong! |
Feature Request
It's much faster to use Bun.js instead of Vite during a test I run. Vite takes about 10-15s to generate the content scripts while Bun is <1s!! Note this happens for any change I make so the developer experience is far better.
Is your feature request related to a bug?
"N/A"
What are the alternatives?
Current solution: Vite
Additional context
Seems not too difficult. Super easy to set up the watch following WXT convension. Using the injectUI code from WXT is a bit tricky.
The text was updated successfully, but these errors were encountered: