New issue
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
update-notifier creates lots of troubles #140
Comments
14 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi.
I understand that the package can be helpful in some cases but its mandatory installment with npm has some bad consequences.
Please see npm/npm#20273
My environment:
OS: Windows
Node: 9.2.0
npm: 5.8.0
Briefly. When I run any npm command in a folder that folder by locked by additional node.exe processes started by update-notifier. That process hangs for a while and it's not clear what is it doing so long. So I have to kill it manually to be able to do anything with the folder. It's terrible experience.
Also it's hard to run npm programmatically. Executing
child_process.exec
withnpm install
for example hangs. I had to rewrite it onto the usage ofspawn
. But even withspawn
we have to carefully useexit
event instead ofclose
asclose
will happen only after node processes spawned by update-notifier exit.Also on Windows there're two packages:
It seems that when I run console under Admin account all both update-notifier's are running!
The text was updated successfully, but these errors were encountered: