-
Notifications
You must be signed in to change notification settings - Fork 322
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
Error: spawn ENAMETOOLONG on Windows 10 #145
Comments
or maybe this one is better: https://github.com/karma-runner/grunt-karma/pull/163/files |
Interesting. Will look into it as soon as I have the time to deep dive into it. To me it looks like karma plugin has solved it by using fork instead of spawn, but that wouldn't do much for this as we don't have a node process, but an actual remote executable. Must be others having this issue too, one would think. |
Any news on this one, we are having the same issue :-( |
We were planning on moving from Toast to KDE's snoretoast, but i'm unsure if this bug is limited to just the binary/program, or if it's a problem with Windows 10's notifications system. Otherwise, no progress has been made on this issue as of yet. |
Could you possibly test out using the latest #134? |
I am using the latest 4.6.1 |
But do you have the same issue if you try using #134 ? |
I'm new to npm, how do I update my node_module with this #134 from npm ? |
Should be |
it says not found :-( |
NB: Try without the So this should work: npm install master-aul/node-notifier |
Ah, didn't know that. Thanks! |
Initially I thought this was due to too many nested directories and the vendor files getting too long path, but I think it might not be the case. Maybe. Could you show me the output command line when getting the error? You can see the output by installing current master:
and run your files by prefixing |
got this today: It's been working great for weeks, not sure why it's now failing Error: spawn ENAMETOOLONG |
On Windows 10 the plugin fails if path is too long:
I found a similiar issue: jsreport/jsreport#202 (comment)
Maybe that helps
The text was updated successfully, but these errors were encountered: