HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
isaacs
npm
Shell2010–2014
isaacs / npm

npm

GitHub Action for interacting with npm

17Distinct people
17Mentions
1Explicit recommenders
25GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

GitHub Action for interacting with npm

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

My favorite thing about npm is its 'utils' code: https://github.com/isaacs/npm/tree/master/lib/utils/ I use code from there at least as often as I use actual modules.

russell_h used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year17 dated mentions

Observed mentions: 2010-07-28 16:58:45 UTC to 2014-03-01 08:38:13 UTC.

0123452010-01-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20102011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 3 mentions; 3 submissions, 0 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20102010-01-01 00:00:00 UTC2011-01-01 00:00:00 UTC404
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC413
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC330
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC523
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
GitHub Actions for NPM This Action for npm enables arbitrary actions with the npm command-line client, including testing packages and publishing to a registry. Usage An example workflow to build, test, and publish an npm package to the default public registry follows: workflow "Build, Test, and Publish" { on = "push" resolves = ["Publish"] } action "Build" { uses = "actions/npm@master" args = "install" } action "Test" { needs = "Build" uses = "actions/npm@master" args = "test" } action "Publish" { needs = "Test" uses = "actions/npm@master" args = "publish --access public" secrets = ["NPM_AUTH_TOKEN"] } Secrets NPM_AUTH_TOKEN - Optional. The token to use for authentication with the npm registry. Required for npm publish (more info) Environment variables NPM_REGISTRY_URL - Optional. To specify a registry to authenticate with. Defaults to registry.npmjs.org NPM_CONFIG_USERCONFIG - Optional. To specify a non-default per-user configuration file. Defaults to $HOME/.npmrc (more info) Example To authenticate with, and publish to, a registry other than registry.npmjs.org: action "Publish" { uses = "actions/npm@master" args = "publish --access public" env = { NPM_REGISTRY_URL = "someOtherRegistry.someDomain.net" } secrets = ["NPM_TOKEN"] } License The Dockerfile and associated scripts and documentation in this project are released under the MIT License. Container images built with this project include third party materials. See THIRD_PARTY_NOTICE.md for details.
Read the full README on GitHub

What Hacker News says

17 sources
still broken. following the instructions on windows, I am getting: D:\repos\js-master\phantomjscloud-backend>npm install npm -g --ca="" npm http GET https://registry.npmjs.org/npm npm http 200 https://registry.npmjs.org/npm npm http GET https://registry.npmjs.org/npm/-/npm-1.4.4.tgz npm ERR! fetch failed https://registry.npmjs.org/npm/-/npm-1.4.4.tgz npm http GET https://registry.npmjs.org/npm/-/npm-1.4.4.tgz npm ERR! fetch failed https://registry.npmjs.org/npm/-/npm-1.4.4.tgz npm http GET https://registry.npmjs.org/npm/-/npm-1.4.4.tgz npm ERR! fetch failed https://registry.npmjs.org/npm/-/npm-1.4.4.tgz npm ERR! Error: CERT_UNTRUSTED npm ERR! at SecurePair.<anonymous> (tls.js:1349:32) npm ERR! at SecurePair.EventEmitter.emit (events.js:92:17) npm ERR! at SecurePair.maybeInitFinished (tls.js:962:10) npm ERR! at CleartextStream.read [as _r
Read the rest
ead] (tls.js:463:15) npm ERR! at CleartextStream.Readable.read (_stream_readable.js:320:10) npm ERR! at EncryptedStream.write [as _write] (tls.js:366:25) npm ERR! at doWrite (_stream_writable.js:219:10) npm ERR! at writeOrBuffer (_stream_writable.js:209:5) npm ERR! at EncryptedStream.Writable.write (_stream_writable.js:180:11) npm ERR! at write (_stream_readable.js:573:24) npm ERR! If you need help, you may report this log at: npm ERR! <http://github.com/isaacs/npm/issues> npm ERR! or email it to: npm ERR! <npm-@googlegroups.com>
In Npm's Self-Signed Certificate is No More
This are a few of the things that I am to following : Server side: Testing: - Expresso [1]: TDD framework for node -- high speed parallel testing! - Zombie.js [2]: fast, headless full-stack testing using Node.js Tools: - load.js [3]: Lazy load your JS - npm [4] a package manager for node - JSDoc [5] Documentation tool - Docco [6] Literate documentation. - underscore [7] provides a lot of the functional programming - node-openid [8] openid. Frameworks: - Express [8] Sinatra inspired web development framework for node [1] http://visionmedia.github.com/expresso/ [2] http://zombie.labnotes.org/ [3] https://github.com/chriso/load.js [4] https://github.com/isaacs/npm [5] https://github.com/micmath/JSDoc [6] https://github.com/jashkenas/docco [7] http://documentcloud.github.com/underscore/ [8] https://github.com/havard/node-openid [9] https://g
Read the rest
In Ask HN: The State of the Javascript Ecosystem?
I would go so far as to say that the greatest strength of node.js is the way people crank out interesting and possibly useful code and stick it on github. This makes it very easy to dive in and start hacking. I would particularly recommend checking out socket.io, and maybe some of the projects using it. It's a way of doing realtime browser-server communication, which uses websockets if the browser supports it, and a variety of increasingly ugly fallbacks on browsers that are old and/or made by Microsoft. You can make some very cool stuff with it. Also, definitely get npm, the node package manager. It makes installing libraries much easier: http://github.com/isaacs/npm
In Ircd.js: A Node.js IRC Daemon

Showing the 15 most recent of 17 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.