Thanks, but I interpret #339 (comment) as meaning this has already been turned down once 😊

@dhh Any chance on reconsidering a section to indicate related projects?

I had a good talk with @gauravtiwari! We're working together on a few ideas, so let's leave this one closed for now. Potentially something good is cooking!

Just to add some context here - @justin808 and I discussed this PR and why alternatives aren't related. Obviously, as an open-source community we can help each other out where possible, but alternatives listed aren't really alternatives - which I think is very clear.

We also discussed a great deal about webpacker_lite since it only works with react_on_rails and hence can't be called webpacker_lite - very confusing to end users. We discussed to either change webpacker_lite to more react_on_rails specific name, so it's more clear that this package is a companion for react_on_rails OR merge it into react_on_rails - much easier to maintain.

@justin808 liked the idea of changing webpacker_lite to webpacker_helpers in the light that perhaps webpacker too can depend on webpacker_helpers going forward. However later I realized that webpacker as a Gem is tiny in itself so this isn't a viable option. This will make maintenance hard and turn off contributors.

Therefore I would suggest to either:

1. Merge webpacker_lite into react_on_rails
2. Consider using webpacker instead without webpack config and provide the one ships with react_on_rails. We can iron out any missing pieces like HMR etc. through PR's

If react_on_rails chooses 2nd option, then we can link it in README under react section 👍

Thanks, @gauravtiwari!

I think option 2 is great.

I will open an issue ticket to get confirmation that we agree on any changes before I do the work of a PR.