Document how jsbundling-rails compares to webpacker #20
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
|
Good guide. Let's split it out into a separate file, then link to that file from the README 👍 |
f193d7d to
fadf9f8
Compare
|
Created a new |
rmacklin
commented
Sep 11, 2021
With `webpacker` previously becoming the default JavaScript bundler in Rails (https://weblog.rubyonrails.org/2019/8/15/Rails-6-0-final-release) it's likely many folks are going to come to the `jsbundling-rails` project wondering how the two compare. So let's document some of the differences that will help developers decide if they want to migrate to `jsbundling-rails` or stick with `webpacker`.
29ea548 to
bfea816
Compare
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.
With
webpackerpreviously becoming the default JavaScript bundler in Rails, I suspect many folks are going to come to thejsbundling-railsproject wondering how the two compare.With that in mind, I think it would be useful to document some of the differences that will help developers decide if they want to migrate to
jsbundling-railsor stick withwebpacker. This PR is a basic attempt to do that :)Something else that could be useful is some sort of migration guide, but I don't intend to include something that specific in this PR, especially given that things are still in flux (this gem is still pre-1.0, and
webpackerappears to be nearing a new major version release).