| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Lightweight smoke test suite that runs common commands so that we can
also have a holistic check during CI.
PR-URL: https://github.com/npm/cli/pull/2959
Credit: @ruyadorno
Close: #2959
Reviewed-by: @nlf
|
|
|
|
PR-URL: https://github.com/npm/cli/pull/2357
Credit: @isaacs
Close: #2357
Reviewed-by: @nlf
|
|
- fix prune target
- fix ci build
- run rebuild after install
PR-URL: https://github.com/npm/cli/pull/2068
Credit: @nlf
Close: #2068
Reviewed-by: @ruyadorno
|
|
There's only a few with the @VERSION@ tag in them, so it's excessive to
rebuild our entire set of docs every time package.json is touched, since
this means redundantly rebuilding docs as part of every release.
|
|
This also reduces the publish file size rather considerably.
|
|
Drop Gatsby, use a simplified custom static site generator that uses GFM
and a template for extremely lightweight docs.
|
|
These links now reflect the reality of the filesystem and their paths.
|
|
There's still a task pending to get it actually up to date with
non-conflicting peer deps and everything updated to remove deprecated
and outdated packages. But at least it builds at all now.
|
|
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
|
|
A few references to the `doc` target were not updated to `docs` in
https://github.com/npm/cli/pull/274 and resulted in `make release`
not building the docs.
PR-URL: https://github.com/npm/cli/pull/546
Credit: @richardlau
Close: #546
Reviewed-by: @mikemimik
|
|
|
|
- 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
|
|
PR-URL: https://github.com/npm/npm/pull/20398
Credit: @kapouer
Reviewed-By: @iarna
|
|
The 'clean' rule calls 'uninstall', which attemts ***destructive***
operation in the host system and fails if run as unprivileged user.
PR-URL: https://github.com/npm/npm/pull/16540
Credit: @metux
Reviewed-By: @iarna
Reviewed-By: @zkat
|
|
The build tools for the documentation need to be built/installed
before the documents, even with parallel builds.
Make has a simple mechanism which was made exactly for that:
target dependencies.
PR-URL: https://github.com/npm/npm/pull/16550
Credit: @metux
Reviewed-By: @iarna
|
|
npx is an npm package runner with a bunch of nice features. While
it is also available on the npm registry as `npx`, it's the sort
of thing that's better off being bundles with npm itself.
Fixes: #6053
PR-URL: https://github.com/npm/npm/pull/17685
Credit: @zkat
Reviewed-By: @iarna
|
|
We were doing `npm install -g` on `make install` and in the `install.sh`
bootstrapper, which now makes a symlink. This updates it to go back to
creating a global copy.
Fixes: #17554
Fixes: #17377
Fixes: #16916
Credit: @iarna
Reviewed-By: @zkat
PR-URL: https://github.com/npm/npm/pull/17626
|
|
|
|
* 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/12146
Credit: @watilde
Reviewed-By: @zkat
|
|
|
|
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
|
|
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.
|
|
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
|
|
|
|
|
|
|
|
This allows make install from a script to override userconfig in particular
|
|
|
|
This is literally how it's always *supposed* to have been working. Yet,
mysteriously, it has not been.
|
|
The better to docs.npmjs.com for great good
|
|
|
|
|
|
|
|
|
|
|
|
Doesn't work that way any more anyway
|
|
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.
|
|
Required so that non-node-core committers can push new npm versions.
|
|
Hasn't been needed, or used at all by anyone, for a VERY long time.
Also, 'npm i npm@1.4' will already get the latest 1.4.x, so I'm not
entirely sure what this was *ever* needed for.
|
|
|
|
|
|
|
|
|
|
Otherwise it fails when you do `npm install` in a fresh repo.
|
|
Otherwise the `make test` command fails to find ronn when generating the
docs for the first time in the prepublish step.
Probably there's a better way to do this, since tarball generation
requires a dev dep to be installed. But this works on Unix at least,
and gets it by for now.
|
|
|
