Question 1

How do I set up local-npm for offline development?

Accepted Answer

Install local-npm globally, start the server with 'local-npm', and set npm's registry to http://127.0.0.1:5080. Once packages are cached, you can install them offline as long as no new versions are needed.

Question 2

local-npm vs Verdaccio: which is better for caching?

Accepted Answer

local-npm is simpler and focused on basic caching and offline use, while Verdaccio is a full private npm registry with features like user authentication. Choose local-npm for straightforward caching, Verdaccio for more advanced registry needs.

Question 3

Can local-npm cache private npm packages?

Accepted Answer

Yes, it can proxy and cache private packages if you have access, but authentication may require additional proxy configuration since it mirrors the main registry's behavior.

Question 4

How does npm publish work with local-npm?

Accepted Answer

npm publish commands are proxied to the main npm registry, so publishing works normally, but the published package won't be cached locally unless it's installed afterward.

Question 5

Is local-npm good for speeding up Docker builds?

Accepted Answer

Yes, by pointing Docker container npm configs to the local server, you can cache dependencies and reduce build times, as detailed in the 'Using with Docker' section.

Question 6

What happens if a package version updates but isn't cached?

Accepted Answer

If you're offline and a new version is published that matches your version range, npm install will fail because local-npm only caches what's been previously installed, requiring an online update first.

local-npm

What is local-npm?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions