As a newcomer to electron, I am currently working on using it to package a react-based app. In an attempt to run electron with a script entry in my package.json file:
"electron-dev": "concurrently \"cross-env BROWSER=none npm start\" \"wait-on http://localhost:3000 && electron . $npm_config_input \"",
This command should execute electron.js (which is specified as the "main" earlier in the package.json), but the challenge arises when trying to pass a command line argument. Although some references suggest that $npm_config_input can be used to pass arguments like this:
% npm run electron-dev --input=file.tif
I have noticed that $npm_config_input remains literal and does not expand for me. Consequently, electron.js receives the exact string $npm_config_input which points to confusion on why it fails to work.
An alternative solution could be:
% npm run electron-dev -- --input=file.tif
However, I am uncertain how to link the input argument to the second concurrently started command. It would be ideal if there was a way to reference something like $1 or $npm_config_input within its definition. Does anyone know of a workaround for this issue?
I am utilizing Windows 10 with git bash for this setup. Most other functionalities seem to be working fine. The environment has nodejs version 12.16.2 installed. Thank you in advance!