Change order of bundler options in README #169
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for the pull request. This is just the order of the libraries we support in no particular order. There is no need to change it and give it a meaning. |
I think they are actually listed in alphabetical order. But of course that doesn't imply any preference. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While Bun looks very exciting (I'm trying it right now) it just hit v1.0 and it is not yet even possible (or at least clearly documented) how to make it work with stimulus (see excid3/esbuild-rails#23)
For newcomers, having it as the first option could lead them to some issues and configuration pain.
I suggest we keep esbuild as the first option as it is literally plug and play at the moment, stable, documented, and has been around for a while.