Skip to content
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

pack: add dryRun option to packDirectory #47

Merged
merged 3 commits into from
Aug 20, 2018
Merged

Conversation

larsgw
Copy link
Contributor

@larsgw larsgw commented Aug 14, 2018

Add dryRun option to packDirectory. This makes it possible to run postscript after the archive has been written to cwd. Something similar could probably be done for packFromPackage.

See https://npm.community/t/592?u=larsgw

Add dryRun option to packDirectory. This makes it possible to run postscript after the archive has been written to cwd.

See https://npm.community/t/592?u=larsgw
Move --dry-run logging closer to original position.
@larsgw larsgw requested a review from a team as a code owner August 14, 2018 13:40
Copy link
Contributor

@zkat zkat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! This is great. Could you add a small test to make sure the original problem isn't happening anymore with this change?

@zkat zkat added semver:patch semver patch level for changes in-progress labels Aug 15, 2018
@larsgw
Copy link
Contributor Author

larsgw commented Aug 15, 2018

It's not the prettiest test: the error message doesn't really work, but I believe that's how test/tap/lifecycle-order.js does it.

@larsgw
Copy link
Contributor Author

larsgw commented Aug 20, 2018

@zkat, I don't think I can request another review with GitHubs interface, or respond to the first one, but I added a test.

Copy link
Contributor

@zkat zkat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Thanks a bunch. This is a great bug fix! 🎉

@zkat zkat changed the base branch from latest to release-next August 20, 2018 22:52
@zkat zkat merged commit 641a5ff into npm:release-next Aug 20, 2018
zkat pushed a commit that referenced this pull request Aug 20, 2018
Add dryRun option to packDirectory. This makes it possible to run postscript after the archive has been written to cwd.

Fixes: https://npm.community/t/592
PR-URL: #47
Credit: @larsgw
Reviewed-By: @zkat
zkat pushed a commit that referenced this pull request Aug 20, 2018
Add dryRun option to packDirectory. This makes it possible to run postscript after the archive has been written to cwd.

Fixes: https://npm.community/t/592
PR-URL: #47
Credit: @larsgw
Reviewed-By: @zkat
isaacs added a commit that referenced this pull request Aug 5, 2019
antongolub pushed a commit to antongolub-forks/npm-cli that referenced this pull request May 18, 2024
* chore: bump @npmcli/template-oss from 3.4.2 to 3.4.3

Bumps [@npmcli/template-oss](https://github.com/npm/template-oss) from 3.4.2 to 3.4.3.
- [Release notes](https://github.com/npm/template-oss/releases)
- [Changelog](https://github.com/npm/template-oss/blob/main/CHANGELOG.md)
- [Commits](npm/template-oss@v3.4.2...v3.4.3)

---
updated-dependencies:
- dependency-name: "@npmcli/template-oss"
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* chore: postinstall for dependabot template-oss PR

* chore: postinstall for dependabot template-oss PR

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: npm team <ops+robot@npmjs.com>
Co-authored-by: Luke Karrys <luke@lukekarrys.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver:patch semver patch level for changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants