-
Notifications
You must be signed in to change notification settings - Fork 121
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
Adds Bun support #392
Adds Bun support #392
Conversation
It will be great to see the Bun support! |
@vitalyliber left to fix tests ;( but you can use my pr to confirm at least this "fast" workaround works for you too |
46d9c33
to
2613df8
Compare
@ElMassimo please review this PR Notes:This is a very naive approach to start using it. I already use it for my projects. |
I found some strange issue: |
Hello, @pftg Currently, bun does not support brotli: oven-sh/bun#267 ViteRuby could work with bun, but we have vite-plugin-rails, which depends on brotli compression currently, may be we should wait some time before brotli will be implemented or conditionally enable brotli in plugin? @ElMassimo any thoughts on this? |
@vladimirtemnikov Yeah, you are right. I had to disable brotli by the way, to use this version. So if this is a hard requirement to support the compress plugin, then there is a workaround. So, for now, I use I think better to start using without brotli to find more issues |
2613df8
to
f3bce48
Compare
@vladimirtemnikov @ElMassimo updated PR, what do you think to add notice in the Readme that it's not compatible with the vite rails plugin and list of supported bun versions? |
Hmm, for development mode, everything was fine, but as soon as I tried to run on Heroku with production mode, the compilation got stuck. I found that when removing RubyPlugin, it's not stuck. I need help to set env to see the real problem. I'll try to look into it later. Will be great to find a guide on how to set up development env for those plugins with bun and with integration testing in the real app. |
Any ideas to bring this forward? Also rails 7.1. has now bun support. Would be nice to when it can also be used in the vite-ruby/rails context. |
Yeah need to check latest tests, maybe now it's working. For now I'm using this approach to use bun https://jtway.co/integrating-bun-with-vite-ruby-for-lightning-fast-frontend-builds-bbd220fefdc0 |
5892ef2
to
d044bd6
Compare
@ElMassimo, with the latest bun, it looks like it works. I'm working on the cleanup in a separate PR jetthoughts#2 |
https://github.com/ElMassimo/vite_ruby/actions/runs/8186414098/job/22384757347?pr=392 - it's a new issue that appeared lately, I will check, but I believe I need to rebase |
89b2388
to
412a06a
Compare
412a06a
to
94f4ec0
Compare
@pftg all green - great job! |
Fantastic, just what I need, but I see this has sat around in a green state for a month+. |
Hi @pftg and other folks! I've added support for a As part of that feature, it felt it was reasonable to add experimental support for Give it a try in The implementation in this pull request is reasonable, but I'd like to minimize the surface area of the library (users typically end up using internals even if they are marked as such). |
d55cc92
to
ebe50b8
Compare
@ElMassimo, could you clarify whether we should close this PR or if you need me to rework some parts? |
Oh, it just adds settings to avoid auto-detection. In this pr, you find encapsulations of package managers at all, and I also added package manager settings too ;) https://github.com/ElMassimo/vite_ruby/pull/392/files#diff-756bec63bbf1c84f70817c5a763e016026db97b00b4b5e99a074dfc2ddb9521cR5 |
Hi @ElMassimo, are there any plans to merge this or make vite_ruby not depend on NodeJS being installed in the system? |
@ElMassimo I forgot to mentione that there are missed more lines, you can check my PR what other changes need to add to make bun works. But I'd suggest to cleanup once and remove duplications with managing js packages, it was a little hard to find all those parts and cleanup it. |
@ElMassimo it would be nice to get this merged and how to enable bun with vite_rails we are using bun to compile assets in prod and works fine but dev still relies on node |
To clarify what I meant with: I'm not interested in merging this refactoring, I'd prefer to keep the library lighter (less classes, smaller footprint). Feel free to open an issue/PR if setting Given the misunderstanding after my reply, I've updated the CONTRIBUTING docs to minimize the chance of similar situations in the future. A few notes from it:
|
Description 📖
Adds support of Bun
Background 📜
Lately, Bun has adopted Vite, so we can use it for compilation assets.