Updated README.md to add related projects #453
Closed
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.
This is similar to how https://github.com/reactjs/react-rails lists related projects. I believe that it's useful to show the community alternatives.
Why did ShakaCode fork rails/webpacker?
3 reasons:
/public
where Webpack will create the manifest and output file. Then you configure your Webpack config to generate a simple manifest that maps the base output names to the possibly fingerprinted versions. Note, unlike Webpacker, Webpacker Lite wants your manifest to NOT contain any host information.For more details on how this project differs from Webpacker and why we forked, please see Webpacker Lite: Why Fork Webpacker?.
The Webpacker Lite README has more details on some subtle differences. For example, Webpacker puts detailed server path information in the manifest.json. Webpacker Lite wants just minimal information in the manifest.json. There's other little differences like that. I wanted Webpacker Lite to make the minimal requirements for the hand-coded Webpack config. Since Webpacker handles the config, it can put logic in either on the Rails or Webpack side.