Strip away arguments used by bnr?

[shrikeh]

I had an issue with bnr whereby I couldn't work out what was changing when I ran webpack via bnr with a specified .env path compared to when I ran it without. Even copying the .env files across till they were identical, webpack would run differently.

After much debugging, I realised that I was running yarn run webpack -p ${ENV_FILE} which became webpack --register --progress --colours -p [dir]/.env, but -p has a specific meaning to webpack. The problem abated when I moved to using --path as that is not an option used with webpack.

Nevertheless it was not obvious for a while that the bnr option was being passed onto webpack. Should options for bnr be stripped from the final call to the script?

[benoror]

do you mind sharing the scripts part of your package.json ?