Webpacker in Production & Customizing Webpacker

Webpacker in production

Deploying Webpacker to production or staging is similar to deploying previous Rails asset tools. Webpacker creates a Rake task, webpacker:compile, which is made part of the existing Rake task assets:precompile, which is likely part of your existing deployment script.

If you are starting a new project without an existing asset pipeline, you can still use assets:precompile for compatibility with older build tools. It’s essentially an alias to webpacker:compile. The compilation uses the RAILS_ENV value to determine which version of the Webpacker configuration to load.

Customizing Webpacker

Webpacker provides great defaults for webpack, but defaults aren’t always enough; you may still need to customize.

One way to customize Webpacker is to change the settings in the config/webpacker.yml file. You can’t add new settings to this file, but you can change the defaults that are already there, including the input and output paths, webpack-dev-server ...