npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

npm-offline-just-testing

v0.0.1

Published

An npm registry proxy that uses your npm cache to retrieve modules, allowing for offline access to any modules you've previously installed pretty much ever.

Downloads

4

Readme

npm-offline Flattr this!experimental

npm-offline

An npm registry proxy that uses your npm cache to retrieve modules, allowing for offline access to any modules you've previously installed pretty much ever.

Super useful when you're moving around a lot and don't always have internet readily available – i.e. when travelling, or at events such as CampJS. It's nice to not need a decent WiFi connection to start a new project.

CLI Usage

Install globally using the following:

$ npm install -g npm-offline

Then you can boot up the proxy server using your newly installed npm-offline command:

$ npm-offline
http://localhost:12644/

Switching Registries

The final step is to point npm to use this registry instead of the default registry.npmjs.org. You don't want to do this permanently, or you'll never get up-to-date module versions. But by using npmrc you can quickly switch between registries. If you're not familiar with it, you can get a basic setup like so:

npm install -g npmrc
mkdir -p ~/.npmrcs
cat ~/.npmrc > ~/.npmrcs/default
cat ~/.npmrc > ~/.npmrcs/local
npmrc local
npm config set registry http://localhost:12644/

You can now switch between the local registry and the remote one using a single command:

npmrc local   # use local modules
npmrc default # use the US registry

This is the same approach advised when using the Australian/European npm mirrors and internal private registries, so it's worth familiarising yourself with it :)

Module Usage

If, for whatever reason, you want to include npm-offline as part of a larger web server you can easily do so.

route = offline(cache, registry)

Creates a route for proxying requests: where cache is your npm cache repository.

route(req, res)

var offline = require('npm-offline')
var express = require('express')
var npmconf = require('npmconf')

var app = express()

npmconf.load({}, function(err, config) {
  if (err) throw err

  app.use(offline(
      config.cache
    , 'http://registry.npmjs.org/'
  ))

  app.listen(12411, function(err) {
    if (err) throw err
  })
})

License

MIT. See LICENSE.md for details.