Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Running nodemon EPERM: operation not permitted, rename on configstore even if I have opt out [windows] #901

Closed
manuel-di-iorio opened this issue Aug 31, 2016 · 3 comments
Closed

Running nodemon EPERM: operation not permitted, rename on configstore even if I have opt out [windows] #901

manuel-di-iorio opened this issue Aug 31, 2016 · 3 comments
Labels
stale no activity for 2 weeks

Comments

@manuel-di-iorio
Copy link

manuel-di-iorio commented Aug 31, 2016 •
edited
Loading

Error thrown even if I had "optOut": true

Error: EPERM: operation not permitted, rename 'C:\Users\User\.config\configstore\update-notifier-nodemon.json.30118632' -> 'C:\Users\User\.config\configstore\update-notifier-nodemon.json'
   at Error (native)
   at Object.fs.renameSync (fs.js:681:18)
   at Function.writeFileSync [as sync]
   etc...
@amelon
Copy link

amelon commented Sep 13, 2016

I have the same issue.
Is there any workaround?

@amelon
Copy link

amelon commented Sep 13, 2016 •
edited
Loading

related issues on update-notifier and write-file-atomic
yeoman/update-notifier#68
npm/write-file-atomic#10

marvinroger added a commit to marvinroger/nodemon that referenced this issue Nov 24, 2016
@marvinroger
🐛 Fix update-notifier race condition
82a636b 
Fix remy#901
@marvinroger marvinroger mentioned this issue Nov 24, 2016
Closed
@paulpatarinski paulpatarinski mentioned this issue Dec 30, 2016
Closed
@ferm10n ferm10n mentioned this issue May 11, 2017
Closed
@stale
Copy link

stale bot commented Dec 5, 2017

This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3

@stale stale bot added the stale no activity for 2 weeks label Dec 5, 2017
@stale stale bot closed this as completed Dec 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale no activity for 2 weeks
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@amelon @manuel-di-iorio