Hello, I am happy to inform you that Webpack has finally been added to Foreman. This step which will help us modernize our front-end code, take advantage of the blooming javascript eco-system, and easily integrate technologies such as ES2015, React, js unit testing and more. A deep-dive will be scheduled soon to explain all the changes, but there are a few details that require your attention for running the current develop branch.
This change requires a slight change to your workflow in the development environment. First, you need to run `npm install` to get all of the needed node modules to install (similar to `bundle install` for gems). Second, to run your server in development environment, you should use `foreman start` which will run both the rails server and the webpack live-reload development server. If you wish to use a non-default setting for the rails server (e.g. using puma), you can set the RAILS_STARTUP environment variable with the relevant command (see Procfile for an example). Please note that running this way will limit the ability to use pry for debugging, as foreman prevents stdin echo. To use with pry, you can run both servers separately in different terminals - run rails as usual in one, and run `./node_modules/.bin/webpack-dev-server --config config/webpack.config.js` in the other. Also, new javascript code should be put in webpack/assets/javascript and placed inside modules, using ES2015 syntax, whenever possible. Old code will be gradually migrated into that location. -- Have a nice day, Tomer Brisker Red Hat Engineering -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
