Closed andreineculau closed 10 years ago
This was addressed by 6eeb5b0 by letting it up to the user to activate the agent. I'm currently cleaning that commit a bit before releasing a new version in NPM.
@andreineculau I just pushed version v0.3.0 to NPM and modifed the Readme explaining how to use this new version since SIGUSR2 is not longer handled by node-webkit-agent. Agent activation is now let up to the user. See: https://github.com/c4milo/node-webkit-agent/commit/8d6873bf3ebb7199321908403a03dd5a44240b91
On file changes, nodemon apparently also sends
SIGUSR2
, which means that if webkit-devtools-agent is loaded, nodemon will start the agent, instead of restarting the processNote: it might be that this would be a better fit as a nodemon issue