Unknown switches '--colors, --progress' - cannot start Watcher as per project documentation

[jmdfm]

Bundler: 1.16.0
Rails: 5.1.4
Webpacker: 3.0.2

The project readme shows under the Development section:

# watcher
./bin/webpack --colors --progress

When executing this command, it fails:

$ ./bin/webpack --colors --progress
Unknown switches '--colors, --progress'

This seems to be related to this hasty PR #843 which removed the proxying of command line switches to the underlying executable.

I'm all for allowing Environment variables to provide configuration, but surely the correct behaviour here is to have Env vars override command line switches rather than just removing command line switches altogether?

Not only is this inconvenient for me as a developer, because I have to wait for the webpacker project to implement missing environment variable analogues for existing command line switches, and this will surely always lag behind the Webpack project, but it's also breaking other projects like react-on-rails.

Please, let the Rails Doctrine apply, and give us back sharp knives.

Happy to work on a PR if consensus is reached.

[jmdfm]

Further information:

This seems like it might be two-pronged issue: it seems that Bundler 1.16.0 is responsible for the 'unknown switches' message, but even if it wasn't the command line arguments still are not being proxied through to the underlying executable in webpacker.

[jmdfm]

Opened an issue with Bundler also: rubygems/bundler#6149

[jmdfm]

Closing this issue as it's totally Bundler that's causing the problem. Sorry folks.