Add neutrino --inspect support for alternative config filenames (#1612)

docs/usage.md

@@ -276,6 +276,12 @@ Or:
 NODE_ENV={production,development,test} neutrino --inspect
 ```
 
+If your Neutrino configuration file is not named `.neutrinojs.js`, specify the filename using `--config`. For example:
+
+```bash
+neutrino --inspect --mode {production,development} --config .custom.neutrino.config.js
+```
+
 As of Neutrino 9, the `--inspect` output when using the official presets is now sufficiently
 self-contained that it can be passed to webpack with no additional changes required.
 

packages/neutrino/bin/neutrino.js

@@ -1,11 +1,18 @@
 #!/usr/bin/env node
 
 const yargsParser = require('yargs-parser');
+const { join } = require('path');
 const neutrino = require('..');
 
 const argv = yargsParser(process.argv.slice(2));
 
 if (argv.inspect) {
+  if (argv.config) {
+    // eslint-disable-next-line global-require, import/no-dynamic-require
+    const middleware = require(join(process.cwd(), argv.config));
+    neutrino(middleware).inspect();
+    process.exit();
+  }
   neutrino().inspect();
   process.exit();
 }
@@ -17,6 +24,8 @@ https://neutrinojs.org/migration-guide/
 
 You may still inspect the generated webpack configuration using:
 neutrino --inspect --mode {production,development}
+or inspect with custom config
+neutrino --inspect --mode {production,development} --config .custom.neutrino.config
 `);
 
 process.exit(1);