| Age | Commit message (Collapse) | Author |
|---|
|
* scripts: replace cli.js with npm-cli.js
* cli: remove unused file cli.js
* docs: replace cli.js with bin/npm-cli.js
PR-URL: https://github.com/npm/npm/pull/12096
Credit: @watilde
Reviewed-By: @zkat
|
|
|
|
PR-URL: https://github.com/npm/npm/pull/16110
Credit: @watilde
Reviewed-By: @iarna
|
|
To support git 2.12.0
Credit: @iarna
Reviewed-By: @zkat
|
|
Credit: @iarna
|
|
|
|
Credit: @zkat
Reviewed-By: @iarna
|
|
Credit: @iarna
|
|
Scripts @iarna uses when updating dependencies in npm.
Credit: @iarna
|
|
|
|
Credit: @iarna
|
|
Credit: @iarna
|
|
|
|
|
|
|
|
|
|
PR-URL: https://github.com/npm/npm/pull/11077
Credit: @iarna
Reviewed-By: ¯\_(ツ)_/¯
Reviewed-By: @othiym23
|
|
PR-URL: https://github.com/npm/npm/pull/9954
|
|
Restore the ability to do one-shot upgrades from the versions of npm
bundled with Node 0.8 to npm@3, which simplifies using Travis with old
Node and new npm, for compatibility testing purposes. Older versions of
npm repack packages on install, which works poorly with the way npm@3
handles bundledDependencies with flat trees.
Fixes: #9668
PR-URL: https://github.com/npm/npm/pull/9981
|
|
This reverts commit 8b58ad09b719295461167a34f666c5aa4d6e26f2.
As it turned out, those partial docs aren't actually used by the
http://docs.npmjs.com site, so there's no sense slowing down the build.
PR-URL: https://github.com/npm/npm/pull/9201
|
|
There was some weirdness going on where, depending on your
local setup during release, you could get unexpected results
during build (specifically, the version on the tarball and zip
corresponded to your global npm's version)
I went ahead and also made it so the npm pack is also done
by the version getting released, to avoid any possible
issues with 2.x vs 3.x
PR-URL: https://github.com/npm/npm/pull/9012
|
|
This is a huge set of mostly mechanical changes. Going forward, all
changes to the npm source base are expected to comply with `standard`,
and it's been integrated into the test suite to enforce that. There are
a few notes below about specific classes of changes that need to be
handled specially for npm's code base.
standard: "Expected error to be handled."
`standard` only expects errors spelled "err" to be handled.
`npm-registry-mock` never actually invokes its callback with an error,
so in some cases I just changed it to be spelled "er" and called it
good.
standard: "Expected a "break" statement before 'case'."
This behavior is actually on purpose, and I don't feel like rewriting
the affected code right now (or, you know, ever). So I added code
comments disabling the checks in the three applicable changes.
standard: "x is a function."
Rebinding functions created via declarations (as opposed to expressions)
is a no-no?
PR-URL: https://github.com/npm/npm/pull/8668
|
|
npm@2's packager can't handle npm@3's bundled node_modules, so
you either have to use a version that we've built for you (eg
one published to the registry) or use the one that you're building.
|
|
|
|
|
|
As a consequence of the various implementations of AWK across platforms,
the use of AWK in `scripts/update-authors.sh` might result in different
sorting behavior on different platforms (i.e. BSD awk on OS X does not
maintain the desired sort- by-first-contribution). So, let's use Perl
instead.
|
|
|
|
|
|
|
|
The better to docs.npmjs.com for great good
|
|
|
|
This fixes the doc builder script so that the appropriate numbers get
printed into the links, and so that 'npm help index' isn't all wonky
in its formatting.
|
|
|
|
Since 1.4.10, the html docs are generated via the marked module. when
doing the usual "make" dance, the build process stops when attempting to
generate the first html doc complaining about a missing
node_modules/.bin/marked.
This patch is a quick'n'dirty copy-pasta of the treatment applied to
load the ronn module but applied to marked. When applied against the
1.4.13 tarball it allows -- at least in a works-for-me manner -- to
generate all the docs.
|
|
|
|
Closes #5111
|
|
|
|
|
|
Closes #4673
|
|
|
|
|
|
|
|
|
|
|
|
Fixes #2004.
|
|
|
|
Makes for weird behavior when installed along with node
|
|
|
|
|
|
|
