You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When pm2 restarts a node process it creates flashing popups. When working with files that automatically save and use a watch this is extremely annoying.
To reproduce:
Create a new repo with git init
Add index.js file containing setInterval to keep the process runnning i.e. a line setInterval(() => console.log('test'), 1000);
At least one commit is needed to reproduce the problem so: git add ./index.js && git commit -m "whatever"
pm2 start index.js --watch
Make a change in index.js. The annoying popups will flash for a split of a second every time the file is updated.
Workaround: Run with pm2 start index.js --watch --no-vizion
This issue was introduced in version 4.5 where Vizion dependency was upgraded from 0.2.13 to 2.x.
Downgrading the dependency to 0.2.13 or disabling vizion with { vizion: false } process.json or when using CLI pm2 ...--no-vizion fixes the issue. I don't know what role vizion plays but it needs to be either replaced with something up to date or vizion needs to be patched/fixed
Also described here but this could've been a different issue originally #2182
The text was updated successfully, but these errors were encountered:
When pm2 restarts a node process it creates flashing popups. When working with files that automatically save and use a watch this is extremely annoying.
To reproduce:
setInterval(() => console.log('test'), 1000);
pm2 start index.js --watch
Workaround: Run with
pm2 start index.js --watch --no-vizion
This issue was introduced in version 4.5 where Vizion dependency was upgraded from 0.2.13 to 2.x.
Downgrading the dependency to 0.2.13 or disabling vizion with
{ vizion: false }
process.json or when using CLIpm2 ...--no-vizion
fixes the issue. I don't know what role vizion plays but it needs to be either replaced with something up to date or vizion needs to be patched/fixedAlso described here but this could've been a different issue originally #2182
The text was updated successfully, but these errors were encountered: