Age | Commit message (Collapse) | Author |
|
Moves workflow to create NPM CLI dependency pull request from npm/node.
Adds input to workflow dispatch trigger
PR-URL: https://github.com/npm/cli/pull/3294
Credit: @gimli01
Close: #3294
Reviewed-by: @darcyclarke
|
|
Drop Gatsby, use a simplified custom static site generator that uses GFM
and a template for extremely lightweight docs.
|
|
|
|
|
|
This removes libnpx, and adds a new command, 'npm exec', which
implements the functionality. As of this change going live, we are
dropping support for the standalone top-level package 'npx'.
Not all of the functionality of the old version of npx is maintained.
The shell fallback functionality is dropped. It's insecure, and not
something we want to support or encourage. If anyone wants it, they
can hack up their .bashrc file themselves.
--no-install is not supported. If the package is not found locally, it
is installed in a predictable location in the cache, rather than
failing. This is something we might want to review, as automatically
installing in the case of misspellings may be a security footgun.
--ignore-existing is dropped. Existing packages are always given
priority.
--quiet or -q can be accomplished by using the --silent npm option, so
it's also dropped.
--npm option is dropped. npx will always use the npm that it ships
with.
--node-arg is dropped. There are other ways to set node options via
environment variables in the Node.js versions we support.
--always-spawn is dropped. npx will always spawn a child process to
execute commands.
The --shell option can be accomplished by using the --script-shell npm
option.
--version and --help are just passed through to npm.
As an added bonus, I noticed that the files in `bin/` were not getting
run. So now we have full coverage for npm-cli.js and npx-cli.js.
PR-URL: https://github.com/npm/cli/pull/1588
Credit: @isaacs
Close: #1588
Reviewed-by: @ruyadorno
|
|
PR-URL: https://github.com/npm/cli/pull/1057
Credit: @ruyadorno
Close: #1057
Reviewed-by: @ruyadorno
|
|
chore(docs): change chmod markdown files
chore(docs): update gitignore
|
|
- chore(docs): remove html from docs build
- feat(docs): migrate new Gatsby site to cli/docs
- chore(docs): fix docs url path
- chore(docs): add new build doc step
- chore(docs): add static linking
- chore(docs): add npm favicon
- chore(docs): update files for tests
- chore(docs): make relative paths absolute
- chore(docs): fix routing on docs dependant tests
- chore(docs): add prepublishOnly docs building step
- chore(docs): add docs/public to .gitignore
- chore(docs): rename dot json markdown files with hyphen names
- chore(docs): clean package.json
- chore(docs): highlight scripts in list
- chore(docs): add strong styles
- chore(docs): fix .json links on markdown
- Added copy to the features page
- Added an install page (copied from existing online docs)
- Added a FeatureLink component to components/links.js
- feat(docs): replace docs sh script with node
- chore(docs): fix docs building process
- chore(docs): docs folder cleanup
PR-URL: https://github.com/npm/cli/pull/274
Credit: @claudiahdz
Close: #274
Reviewed-by: @ruyadorno
|
|
Several changes to the test suite to support running tests in parallel,
bringing the overall test time down considerably.
- Replace all literal 1337 and 1234 ports with a custom per-process port
assignment based on the TAP_CHILD_ID environment variable.
- Add common.pkg as a per-test working directory instead of polluting
__dirname or accidentally reusing the same working directory for
multiple tests.
- Rework test config handling so that tests don't rely on config setup
being run in a particular order.
- Remove the npm-registry-couchapp tests, since it (a) relies on
CouchDB, (b) is no longer a reliable indicator of registry
compatibility, and (c) is already superceded in most cases by tests
that use npm-registry-mock. (A test suite that runs against a
reference implementation is a thing that should exist, but not here.)
- Remove the fake-registry logging when TAP_CHILD_ID is set, since this
is extremely hard to make sense of when running multiple tests in
parallel.
When Node v6 compatibility is dropped in npm v7, we can upgrade to the
latest version of tap for a bit more speed, dropping Domains (and the
associated deprecation warnings), and a fancier test reporter.
|
|
|
|
PR-URL: https://github.com/npm/npm/pull/19879
Credit: @watilde
Reviewed-By: @zkat
|
|
This will help avoid an accidental publish or commit filled with
code coverage data
Fixes: https://github.com/npm/npm/issues/12873
Credit: @TheAlphaNerd
PR-URL: https://github.com/npm/npm/pull/12878
Reviewed-By: @zkat
|
|
nyc has come a long way over the last few months, and now only one test
is wily enough to detect its presence. Handle that, and we get coverage
information about the CLI!
Credit: @othiym23
PR-URL: https://github.com/npm/npm/pull/11444
Reviewed-By: @zkat
Reviewed-By: @iarna
Reviewed-By: @othiym23
|
|
Tool to generate fixtures from folders and module for creating and tearing
down filesystem fixtures easily.
Credit: @iarna
PR-URL: https://github.com/npm/npm/pull/11292
Reviewed-By: @zkat
Reviewed-By: @othiym23
|
|
Also, clean out the docs and prune the tree before making a release
tarball, to keep as much cruft as possible out of the release tarball.
PR-URL: https://github.com/npm/npm/pull/10798
Credit: @othiym23
|
|
Previously it was only used in tests, but we needed a modern pass through
stream to provide buffering for 0.8 http streams, which have a bug around
backpressure.
|
|
PR-URL: https://github.com/npm/npm/pull/10180
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
The API is awkward, brittle, and frequently counterintuitive. Having it
documented sets an unrealistic expectation of it being a supported /
encouraged thing for developers outside the team to use. Until we have
an API we should stand behind, having it be undocumented is actually a
net win because people won't be misled into thinking they're gonna have
a good time by using it.
|
|
Add t.contains() as alias to t.match(), and switch to version of `same`
that supports cycles in the object graph.
|
|
|
|
tap->nyc->yargs added a bunch of new deps that we now need to ignore
|
|
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
|
|
|
|
|
|
|
|
|
|
It's now used via this chain:
npm-registry-couchapp -> couchapp -> connect -> finalhandler -> unpipe
|
|
Also add it to the test stanzas in package.json.
|
|
|
|
Unfortunately small changes to the installer can result in different
trees with git dependencies -- all are valid, but some are lossier than
others. Handle all three valid alternatives in the test so it's not so
sensitive to raciness, and also not coupled too tightly to the
implementation.
|
|
|
|
|
|
|
|
All changes should be confined to the test repo.
|
|
The better to docs.npmjs.com for great good
|
|
|
|
|
|
|
|
|
|
|