I’m no expert at all on nodejs and npm but doing an `npm update` feels more appropriate than deleting the entire cache, or am I missing something?
A bug has been filed: https://bugs.launchpad.net/snapcraft/+bug/1660614 Thanks, Geoffroy From: [email protected] [mailto:[email protected]] On Behalf Of Stephen Stewart Sent: Tuesday, January 31, 2017 12:30 PM To: Snapcraft <[email protected]> Subject: Re: Issue with snapcraft nodejs plugin (and the local npm cache) Hi, Another quick fix: I believe the nodejs plugin uses the global npm cache, which will be ~/.npm[1], so you could try deleting that folder. Consider having the nodejs plugin support per project .npmrc so users can set cache options themselves rather than set via args in the plugin. [1] https://docs.npmjs.com/cli/cache#cache Hope this helps, Stephen On Tue, Jan 31, 2017 at 12:05 AM Leo Arias <[email protected]<mailto:[email protected]>> wrote: Hello Geoffroy, thanks for all the information. Can you please report a bug? https://bugs.launchpad.net/snapcraft/+filebug pura vida. -- Snapcraft mailing list [email protected]<mailto:[email protected]> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
-- Snapcraft mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
