Skip to content

chore: log if npm deprecate does not match any version#7472

Closed
mbtools wants to merge 2 commits into
npm:latestfrom
mbtools:patch-1
Closed

chore: log if npm deprecate does not match any version#7472
mbtools wants to merge 2 commits into
npm:latestfrom
mbtools:patch-1

Conversation

@mbtools

@mbtools mbtools commented May 5, 2024

Copy link
Copy Markdown
Contributor

If the package specification does not match any existing version, a verbose message is added to the log.

References

Closes #7180

If the package specification does not match any existing version, a verbose message is added to the log.

Closes #7180
@mbtools
mbtools requested a review from a team as a code owner May 5, 2024 10:31
@mbtools
mbtools marked this pull request as draft May 5, 2024 10:46
@mbtools

mbtools commented May 5, 2024

Copy link
Copy Markdown
Contributor Author

too much work to figure out which tests need to be adapted

@mbtools mbtools closed this May 5, 2024
@mbtools
mbtools deleted the patch-1 branch May 5, 2024 12:56
@wraithgar

Copy link
Copy Markdown
Contributor

I think the test failures were preventing you from logging w/ the old log-shim. We added that guard when we finished the logging refactor. You will want to use proc-log. You can look in lib/commands/install.js for an example

const { log } = require('proc-log')

Comment thread lib/commands/deprecate.js
ignoreBody: true,
}))
} else {
log.verbose('no version found for', p)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I could see an argument being made that this should be a warn

mbtools added a commit to mbtools/npm-cli that referenced this pull request May 5, 2024
If the package specification does not match any existing version, a verbose message is added to the log.

## References

Ref npm#7472
Closes npm#7180
wraithgar pushed a commit that referenced this pull request May 6, 2024
If the package specification does not match any
existing version, a warning message is added to the log.

## References

Ref #7472
Closes #7180
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 this pull request may close these issues.

[BUG] Running npm deprecate package@version "reason" silently fails when no versions match

2 participants