-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: document dependencies
script
#5095
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -39,7 +39,7 @@ There are some special life cycle scripts that happen only in certain | |
situations. These scripts happen in addition to the `pre<event>`, `post<event>`, and | ||
`<event>` scripts. | ||
|
||
* `prepare`, `prepublish`, `prepublishOnly`, `prepack`, `postpack` | ||
* `prepare`, `prepublish`, `prepublishOnly`, `prepack`, `postpack`, `dependencies` | ||
|
||
**prepare** (since `[email protected]`) | ||
* Runs any time before the package is packed, i.e. during `npm publish` | ||
|
@@ -71,6 +71,10 @@ situations. These scripts happen in addition to the `pre<event>`, `post<event>`, | |
**postpack** | ||
* Runs AFTER the tarball has been generated but before it is moved to its final destination (if at all, publish does not save the tarball locally) | ||
|
||
**dependencies** | ||
* Runs AFTER any operations that modify the `node_modules` directory IF changes occurred. | ||
* Does NOT run in global mode | ||
|
||
#### Prepare and Prepublish | ||
|
||
**Deprecation Note: prepublish** | ||
|
@@ -96,6 +100,10 @@ The advantage of doing these things at `prepublish` time is that they can be don | |
* You don't need to rely on your users having `curl` or `wget` or | ||
other system tools on the target machines. | ||
|
||
#### Dependencies | ||
|
||
The `dependencies` script is run any time an `npm` command causes changes to the `node_modules` directory. It is run AFTER the changes have been applied and the `package.json` and `package-lock.json` files have been updated. | ||
|
||
### Life Cycle Operation Order | ||
|
||
#### [`npm cache add`](/commands/npm-cache) | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what env vars are available to help explain what changes occurred?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good question. as of today, none. i don't intend to export anything in the initial release of this feature.
we should discuss this in an rfc call and try to come to a consensus about what information is desirable here so that we don't have to ship a semver-major to change what we export later