We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
i'm developing an app using a forked Electron version, specifically the ow-electron package, https://www.npmjs.com/package/@overwolf/ow-electron
Also setting the electronPath in electronmon packages.json section, doesn't seem nodemon is starting using ow-electron
electronPath
electronmon
"electronmon": { "patterns": [ "!**/**", "src/main/**" ], "logLevel": "verbose", "electronPath": "./node_modules/bin/ow-electron" }
tried with simple ow-electron also.
ow-electron
I'm using it with the electron-react-boilerplate https://github.com/electron-react-boilerplate/electron-react-boilerplate
Replacing electromon with ow-electron here, launch the application with ow-electron
"start:main": "cross-env NODE_ENV=development electronmon -r ts-node/register/transpile-only .",
I'm not an Electron expert so probably i'm missing something :)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
i'm developing an app using a forked Electron version, specifically the ow-electron package, https://www.npmjs.com/package/@overwolf/ow-electron
Also setting the
electronPath
inelectronmon
packages.json section, doesn't seem nodemon is starting using ow-electrontried with simple
ow-electron
also.I'm using it with the electron-react-boilerplate https://github.com/electron-react-boilerplate/electron-react-boilerplate
Replacing electromon with ow-electron here, launch the application with ow-electron
"start:main": "cross-env NODE_ENV=development electronmon -r ts-node/register/transpile-only .",
I'm not an Electron expert so probably i'm missing something :)
The text was updated successfully, but these errors were encountered: