Skip to content
Snippets Groups Projects
Commit 2076c557 authored by aschmitz's avatar aschmitz Committed by Eugen Rochko
Browse files

Configure webpack to poll for changes in development (#5040)

* Configure webpack to poll for changes in development

Vagrant on Linux/macOS hosts shared files via NFS, which doens't
support inotify-based watching of files. This tweak makes webpack
check for changes every second, and rebuild if necessary. This
removes the need to restart Foreman every time a frontend file
changes. Note that rebuilding is still a relatively lengthy
process.

The polling frequency can be changed to taste.

* Only poll in Vagrant

This tests for the presence of the VAGRANT environment variable to
determine whether or not we're in Vagrant. It is set in .env.vagrant,
which is set up to be included in the Vagrantfile.
parent d40c9140
No related branches found
No related tags found
No related merge requests found
......@@ -4,6 +4,17 @@ const merge = require('webpack-merge');
const sharedConfig = require('./shared.js');
const { settings, output } = require('./configuration.js');
const watchOptions = {
ignored: /node_modules/,
};
if (process.env.VAGRANT) {
// If we are in Vagrant, we can't rely on inotify to update us with changed
// files, so we must poll instead. Here, we poll every second to see if
// anything has changed.
watchOptions.poll = 1000;
}
module.exports = merge(sharedConfig, {
devtool: 'cheap-module-eval-source-map',
......@@ -26,8 +37,6 @@ module.exports = merge(sharedConfig, {
headers: { 'Access-Control-Allow-Origin': '*' },
historyApiFallback: true,
disableHostCheck: true,
watchOptions: {
ignored: /node_modules/,
},
watchOptions: watchOptions,
},
});
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment