Skip to content

Conversation

rbnayax
Copy link
Contributor

@rbnayax rbnayax commented Sep 20, 2025

If someone pinned a version, they might not want to update it. In that case, if using a new flag, it will be skipped

@rbnayax
Copy link
Contributor Author

rbnayax commented Sep 21, 2025

@raineorshine the prints I added mess up with the progress bar printing. Any suggestions on how to deal with it?

@raineorshine
Copy link
Owner

Hi, thanks for your submission.

This functionality is better achieved in user land, without adding to the public api.

See: filterVersion

@rbnayax
Copy link
Contributor Author

rbnayax commented Sep 22, 2025

I agree that it can be achieved by that, and we are already using it (filterResults actually) but this requires from the user to write custom code and use the js config. I believe that this feature should be easier to achieve via a flag. The filter logic should be used for more complex logic

@raineorshine
Copy link
Owner

That's reasonable, but ultimately it's not in alignment with the design philosophy of npm-check-updates. We already have a ton of options, so I'm not willing to add another option for something that can be accomplished with a custom filter function.

We also have --target semver which respects pinned versions.

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.

2 participants