Age | Commit message (Collapse) | Author |
|
PR-URL: https://github.com/npm/npm/pull/10337
Credit: @iarna
Reviewed By: @othiym23
|
|
PR-URL: https://github.com/npm/npm/pull/9443
|
|
PR-URL: https://github.com/npm/npm/pull/10036
|
|
PR-URL: https://github.com/npm/npm/pull/10176
|
|
Fixes #9460, specifying the default command run by "npm start" and the
fact that you can pass it arguments.
PR-URL: https://github.com/npm/npm/pull/10097
|
|
PR-URL: https://github.com/npm/npm/pull/10021
|
|
Default Configs
PR-URL: https://github.com/npm/npm/pull/10020
|
|
PR-URL: https://github.com/npm/npm/pull/10015
Fixes: #7600
|
|
the NODE_ENV.
The following is the condition of setting the value of the development / production option.
npm install
+ dev: true
+ prod: true
--only=dev
+ dev: true
+ prod: false
--only=prod || NODE_ENV=production
+ dev: false
+ prod: true
PR-URL: https://github.com/npm/npm/pull/9835
Fixes: #9463
|
|
`node-gyp` looks for `binding.gyp`.
PR-URL: https://github.com/npm/npm/pull/9820
|
|
PR-URL: https://github.com/npm/npm/pull/9759
|
|
PR-URL: https://github.com/npm/npm/pull/9714
|
|
PR-URL: https://github.com/npm/npm/pull/9595
Fixes: #9208
|
|
PR-URL: https://github.com/npm/npm/pull/9761
|
|
|
|
The behavior described here has been inaccurate for a long time. Not only was
the `wscript` bit removed from `read-package-json` over 2 years ago, the
`install` script is what is set to the default (now `node-gyp rebuild`), not
`preinstall`.
Fixes #9583
PR-URL: https://github.com/npm/npm/pull/9584
|
|
I was a bit confused when I found out that `.gitignore` files
are treated as replacements for `.npmignore` files even in
subdirectories, given that the documentation basically only
talks about `.npmignore` in the root directory.
I hope this clears things up a little for other users.
PR-URL: https://github.com/npm/npm/pull/9492
|
|
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.
|
|
PR-URL: https://github.com/npm/npm/pull/9386
|
|
PR-URL: https://github.com/npm/npm/pull/9200
|
|
PR-URL: https://github.com/npm/npm/pull/9011
|
|
PR-URL: https://github.com/npm/npm/pull/9011
|
|
PR-URL: https://github.com/npm/npm/pull/9024
|
|
PR-URL: https://github.com/npm/npm/pull/9024
|
|
PR-URL: https://github.com/npm/npm/pull/9108
|
|
PR-URL: https://github.com/npm/npm/pull/9037
Fixes: https://github.com/npm/npm/issues/8704
|
|
PR-URL: https://github.com/npm/npm/pull/9002
|
|
PR-URL: https://github.com/npm/npm/pull/9022
|
|
Fixes #8036
PR-URL: https://github.com/npm/npm/pull/8917
|
|
* The command line command was broken
* wrote tests for the command itself
* added documentation for both the API and CLI versions
PR-URL: https://github.com/npm/npm/pull/8800
|
|
PR-URL: https://github.com/npm/npm/pull/8760
|
|
PR-URL: https://github.com/npm/npm/pull/8754
|
|
the wording here is a little confusing. after talking to @iarna on irc,
I am submitting this docpatch which i think describes more accurately
the use of both `directories.bin` and `bin`.
PR-URL: https://github.com/npm/npm/pull/8708
|
|
Closes #8620
(cherry picked from commit a2106bf)
|
|
|
|
put @ inside <@scope>
simplify completion usage
add [@<version>] to edit
remove extraneous from install
|
|
|
|
|
|
Fixes: #8557
PR-URL: https://github.com/npm/npm/pull/8609
|
|
Fixed: #8365
PR-URL: https://github.com/npm/npm/pull/8565
|
|
|
|
PR-URL: https://github.com/npm/npm/pull/8554
|
|
Corrected a typo in _peerDependencies_: "a host tool or library" rather than "an host tool or library"
PR-URL: https://github.com/npm/npm/pull/8462
|
|
Detail effect of setting NODE_ENV=production to command and how to negate
PR-URL: https://github.com/npm/npm/pull/8421
|
|
Thanks, Kenan! (typo found in
https://github.com/npm/npm/commit/14aceddaf15f8310b6ec29c2c7dafac7695ca22b#commitcomment-11410241).
|
|
|
|
|
|
Fixes #7906. This was requested to allow authors to require scripts to be
true prior to bumping the version number for release. For instance, by
running the test suite.
As bumping the version number is a typical action immediately prior to
releasing a new version, this acts as a `prepublish` that ties to the actual
act of publication, versus the `prepublish` lifecycle, which is run under
some install-time circumstances as well.
|
|
|
|
|