-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
EPERM: operation not permitted #709
Comments
Yeah, they're all trying to access the config setting for the update notification. If you can stagger the booting of the 4 nodemons, maybe it'll help? |
Ok, i'll think about it.
|
To keep nodemon up to date. You can disable it using this On Thu, 29 Oct 2015 19:03 Nikolay notifications@github.com wrote:
|
Oh, I see, so it constantly checks for updates like Google Chrome does.
|
The
|
Nope, it didn't work.
|
Since there's no way to prevent nodemon from writing that
var args = process.argv.slice(2)
var delay = args[0]
if (typeof delay === 'undefined')
{
return console.error('[sleep] delay (in ms) not specified')
}
if (delay != parseInt(delay))
{
return console.error('[sleep] invalid delay: "' + delay + '"')
}
console.log('[sleep] sleeping for ' + delay + ' milliseconds')
setTimeout(function()
{
console.log('[sleep] woken up')
process.exit(0)
},
delay) |
update-notifier/index.js:48 has if (this.config.get('optOut') || 'NO_UPDATE_NOTIFIER' in process.env || process.argv.indexOf('--no-update-notifier') !== -1) {
return;
} So I configured my shell Git for Windows I can also confirm that appending the option to your nodemon command works too. "watch:build:scripts": "nodemon --watch src/ --ext * --exec \"npm run build:scripts\" --no-update-notifier", |
Suggested solution above doesn't work. When launching multiple nodemon processes with --no-update-notifier argument there is still EPERM: operation not permitted renaming update-notifier-nodemon.json.{some-string} to update-notifier-nodemon.json It's due to the fact that in update-notifier package from nodemon's package.json (0.5.0) there is always writing-file-async in Configstore constructor in UpdateNotifier constructor (line 34), so the flag doesn't work. It is solved in update-notifier package in newer versions (eg. 2.2.0) and --no-update-notifier has influence there on creating Configstore, while it's public conctract remains untouched. |
I have this same issue, running node in docker. I get
Node: 8.4.0 Hopefully @padzikm or someone gets a fix soon. |
This issue mainly focuses on the Any ideas what is causing this one?
|
I'm having this error randomly.
Usually the first time I run
nodemon
.The second try works.
(I'm running 4 nodemons in parallel if it matters)
I've tried setting the aforementioned folder's permissions but it didn't take effect.
The text was updated successfully, but these errors were encountered: