Npm operational incident, 6 Jan 2018

Re:Npm operational incident, 6 Jan 2018 by acemarke on Sunday January 07, 2018 @04:49PM (#16092941)

Committing your `node_modules` is a bad idea. The best answer is to either use an offline cache of package tarballs that have been committed to your repo, or an NPM caching proxy.

Yarn has an "offline mirror" feature built in, and Shrinkpack is a tool that can create an offline mirror based on an npm-shrinkwrap.json file.

I wrote about using Yarn's offline mirror here: http://blog.isquaredsoftware.com/2017/07/practical-redux-par...

[ Parent | on HN ]

Re:Npm operational incident, 6 Jan 2018 by djsumdog on Sunday January 07, 2018 @04:59PM (#16092986)

I know you can use JFrog/Artifactory to cache pulls of Jar files from maven repos, as well as Docker images. Does JFrog support node?

[ Parent | on HN ]

Re:Npm operational incident, 6 Jan 2018 by Qerub on Sunday January 07, 2018 @06:12PM (#16093316)

Yes, JFrog Artifactory supports npm and so does Sonatype Nexus. More info:

https://www.jfrog.com/confluence/display/RTF/Npm+Registry https://help.sonatype.com/display/NXRM3/Node+Packaged+Module...

[ Parent | on HN ]

Re:Npm operational incident, 6 Jan 2018 by acemarke on Sunday January 07, 2018 @06:06PM (#16093288)

I haven't actually used an NPM caching proxy myself. It looks like Artifactory does support acting as an NPM proxy. The other tools I've heard of are Sinopia, Verdaccio, and local-npm.

Addy Osmani has a related article at https://addyosmani.com/blog/using-npm-offline/ .

[ Parent | on HN ]

Re:Npm operational incident, 6 Jan 2018 by vePhi4le on Sunday January 07, 2018 @07:09PM (#16093632)

yes: https://www.jfrog.com/confluence/display/RTF/Npm+Registry

[ Parent | on HN ]