breautek commented on issue #423: URL: https://github.com/apache/cordova/issues/423#issuecomment-1625422632
> Hello there Norman, running the command in a regular shell prompt works fine. Is it something to do with the snap version of npm/node, I wonder? I'll try to repro with a non-snap version tomorrow. I do know that running apps under snap uses AppArmour which gives processes a fine grain control over what they can or can't do, or what directories/files they can access or can't access. I personally don't use snap cause often times these settings appears to be misconfigured for proper usage... at least that was my experience with them. But if you're running a snap version, and that's the version running in the same regular prompt, then I would have expected the issue to reproduce if it was an apparmour sandbox issue. I use `nvm` myself, which to me is the easiest way to manage using different node versions. So if you want to try different environments, I'd give that a go. If all else fails... I think we'll need to run the command line under the node debugger, or add print statements to try to figure out where that error is coming from exactly. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
