I'd suggest the following:
Provide Rails support for the webpack module bundler for client-side assets.
- Provide no interference with the legacy Asset Pipeline.
/app/assets contains files used by the Asset Pipeline.
- Static files created for development.
- Running the webpack-dev-server for providing hot-reloadable files for development.
- Static, hashed files created for production deployment, using the chunkhash technique for asset caching.
- Via the Rails
/config/webpack.rb, Allow configuration of the controller and view helpers in a convenient manner that does not mandate any particular location of the webpack configuration files nor the subdirectory under the
/public directory for deployment.
A gem like the above can be usable for any Rails 3.x and greater project.
Optional for Rails 5.1
- Provide a generator to create the simplest possible example of using Webpack for assets.
Out of Scope
- Anything beyond a basic webpack config, as the maintenance of this config would be far greater than the basics needed to support the scope of the gem.