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

no dry-run option for npm #820

Open
eknowles opened this issue Jul 15, 2023 · 2 comments · Fixed by #821
Open

no dry-run option for npm #820

eknowles opened this issue Jul 15, 2023 · 2 comments · Fixed by #821

Comments

@eknowles
Copy link
Contributor

there's no way to dry-run publish npm packages, as this options is available in publib-npm

eknowles added a commit to eknowles/publib that referenced this issue Jul 15, 2023
.npmrc are also created in a temp dir so as to not
overwrite existing npmrc in home directory

fixes cdklabs#820 cdklabs#819
eknowles added a commit to eknowles/publib that referenced this issue Jul 15, 2023
.npmrc are also created in a temp dir so as to not
overwrite existing npmrc in home directory

fixes cdklabs#820 cdklabs#819
github-merge-queue bot pushed a commit that referenced this issue Jul 27, 2023
* feat(publib-npm): allow dry run and support `_auth` token type

.npmrc are also created in a temp dir so as to not
overwrite existing npmrc in home directory

fixes #820 #819

* docs(readme): update `publib-npm` options
@udondan
Copy link

udondan commented Mar 20, 2024

as to my knowledge this had been reverted, so this should be opened up again.

@mrgrain mrgrain reopened this Mar 21, 2024
@udondan
Copy link

udondan commented Mar 21, 2024

As a workaround, I have found you can set the env var npm_config_dry_run=true to convince npm to make a dry run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants