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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 11:34:28 AM 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

4 sources
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
I posted this info as a comment on the guy's blog (still awaiting moderation), but I thought you might find it interesting too, the point being that amazing things are possible with JavaScript and node.js, but if you're thinking single-file scripts with a tangled nest of callbacks and prototypal inheritance chains+constructors that are hard to keep straight, well ... there are better ways ......... :-D As a JavaScript developer working with node.js (and client side scripts too, of course), I’d like to recommend a couple of related things: Joose3 — an object system for JavaScript which allows truly classful programming; use it to implement all sorts of meta-programming magic with ease: http://joose.it/ http://openjsan.org/doc/s/sa/samuraijack/Joose/3.011/lib/Joo... JooseX.CPS — a continuation-passing-style "trait" for Joose classes which
Read the rest
helps prevent your asynchronous code from turning into "callback spaghetti": http://joose.it/blog/2010/08/02/asynchronous-aka-non-blockin... http://openjsan.org/doc/s/sa/samuraijack/JooseX/CPS/0.11/lib... Joose is open source, works with both node.js and in browsers, and there are various ways to install and leverage its libraries, e.g. npm: http://github.com/isaacs/npm This isn’t an advertisement. I started exploring node.js in early 2010, and my "discovering" Joose was a real boon as I was looking to do some complicated things that seemed daunting when trying to express the concepts in terms of prototypal inheritance. Not everyone finds it attractive, but I’m always happy to spread the word in hopes that Joose can make someone else’s life and programming projects a little less stressful, which is what it's done for me.
In Drinking the Node.js Kool-Aid

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.