Add --skip-npm flag #198
Merged
Add --skip-npm flag #198
Conversation
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
Have Lerna update all versions and dependencies where required in `package.json` files without actually publishing the changes to NPM. This is useful for publishing manually, which is necessary to do periodically to get README updates to show up on npmjs.com (until https://github.com/npm/newww/issues/389 is resolved). This is a workaround for lerna#64. This was proposed in lerna#127.
|
Nice, this looks awesome. Thanks! |
| versions and dependency versions, but it will not actually publish the | ||
| packages to npm. | ||
|
|
||
| This flag can be combined with `--skip-git` to _just_ update versions and |
There was a problem hiding this comment.
Could be useful to give the example of just wanting to push a readme update
gigabo
added a commit
to gigabo/react-server
that referenced
this pull request
Jun 10, 2016
This picks up some patches that will help us out: - lerna/lerna#181 - lerna/lerna#196 - lerna/lerna#198 - lerna/lerna#199
gigabo
added a commit
to redfin/react-server
that referenced
this pull request
Jun 13, 2016
* Upgrade lerna-2.0.0-beta.18 This picks up some patches that will help us out: - lerna/lerna#181 - lerna/lerna#196 - lerna/lerna#198 - lerna/lerna#199 * Use `lerna clean` for `npm run nuke`
davidalber
pushed a commit
to davidalber/react-server
that referenced
this pull request
Jul 24, 2016
* Upgrade lerna-2.0.0-beta.18 This picks up some patches that will help us out: - lerna/lerna#181 - lerna/lerna#196 - lerna/lerna#198 - lerna/lerna#199 * Use `lerna clean` for `npm run nuke`
|
@thejameskyle @gigabo Is there a way to default this setting using lerna.json? We're using lerna for closed-source code that we don't want to publish to NPM at all. |
|
This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Have Lerna update all versions and dependencies where required in
package.jsonfiles without actually publishing the changes to NPM.This is useful for publishing manually, which is necessary to do periodically to get README updates to show up on npmjs.com (until https://github.com/npm/newww/issues/389 is resolved).
This is a workaround for #64.
This was proposed in #127.