Integrations › Search and stores › npm

Turn your npm into build-in-public posts

npm is the public registry where JavaScript packages are published and installed. FoxPlug reads what you did there, scores it, and tells you what to fix, what to say and what to skip. Nothing posts until you approve it.

Read onlyChecked with a real account

1What FoxPlug reads from npm

These are the exact things it reads, and nothing else.

WhatThe details it takes
The package's registry entrythe latest version from dist-tags, the list of published versions (the last 30 are kept for comparison) and the publish time of the latest version
Downloads in the last weekthe download count point for last-week, kept as a number on the connection (optional: a failure is ignored)
Total downloads since 2015-01-10the download count from 2015-01-10 to today, used for the download milestones
The package name you typedup to 5 names, comma separated, including @scope/name

2Moments it finds, and what each becomes

A moment is one thing that happened in npm worth a second look. Each one is scored, then it becomes a post, a changelog entry, a thing to fix or an idea to email, or it is skipped.

Changelog

a new version becomes the latest tag of a package FoxPlug has read before

The moment is titled like this: Released my-lib 2.1.0

Your made-up package my-lib moves from 2.0.9 to 2.1.0. On the next Check for what's new FoxPlug writes 'Released my-lib 2.1.0' with the line 'my-lib 2.1.0 is published on npm.' and the package link. It is an update that can become a post and a changelog entry.

Post

total downloads cross 100, 500, 1,000, 5,000, 10,000, 50,000, 100,000, 500,000, 1M, 5M, 10M, 50M or 100M

The moment is titled like this: my-lib passed 10,000 downloads

my-lib has 12,480 downloads in total at the last read. FoxPlug writes 'my-lib passed 10,000 downloads' with 'my-lib now has more than 10,000 downloads (12,480 at the last read).' Each step fires once.

3How the brain uses it

The rules below are the ones that apply to npm. The same rules, with worked examples, are on the brain page.

4Set up npm in a few steps

Access: none: a public package name only (no login, no key). What to give it: package name only, nothing secret (comma-separate up to 5).

  1. Open npmjs.com and find your package.
  2. Copy its exact name from the page (for example your-package or @scope/your-package).
  3. Paste the name into FoxPlug. To watch several packages, separate them with commas (up to 5).
  4. Press Connect.

5Limits worth knowing

Where it stops, so nothing surprises you.

6What it never reads

Read only means read only, and the list below is what the code leaves alone.

  • Any login or token of yours (it needs only a package name)
  • Your package's source or tarball contents (only the registry entry and download counts are fetched)
  • Private packages (only the public registry and public download counts are called)

7How npm differs from the tools next to it

PyPI is near-identical in shape, but npm milestones count total downloads since 2015-01-10 while PyPI milestones count downloads in the last month (from pypistats), and npm names may be @scope/name.

8Questions

Does FoxPlug need my npm login?

No. You paste only the package name. FoxPlug reads the public registry entry and the public download counts.

What counts as a download milestone?

The total downloads since 2015-01-10. When it crosses a step such as 1,000 or 100,000 FoxPlug writes one update for that step, once.

Can I watch more than one package?

Yes, up to five, separated by commas. Scoped names like @scope/name work.

Will it tell me about new versions I published before connecting?

No. The first read records where things stand; only versions that appear after that are written as new releases.

Checked with a real connected account of ours: real public read of express 5.3.0 with a 100,000,000-download milestone (T1670, T1683).

FoxPlug reads this tool only when you press Check for what's new, and only to read. Plans and limits are on the pricing page. Questions: support.