Allow by-package overrides for semver level and possibly other config

[brettz9]

• I have searched for similar issues
• I am using the latest version of npm-check-updates
• I am using node >= 10.17

---

Current Behavior

Using reject, I can wholly prevent updates on a particular package.

Expected Behavior

I'd like to be able to get patch or minor fixes for a given package, while still preventing it from having major bumps (e.g., bootstrap).

I'm cool if this is passed right away to the idea heap--just would be a nice to have, thanks!

[raineorshine]

Cool! So would this basically be --semverLevel on a per-package basis?

[brettz9]

Yeah--I guess it would be less of a reject (or filter) and more of an "override" (as with the former, regexes and CSV could be useful here too, though not critical for my purposes).

Other flags, per a cursory review, that look of conceivable use with overriding besides semverLevel, might be minimal, newest, pre, and greatest and maybe dep too (e.g., if indicating say eslint devDeps. should be updated, not eslint peerDeps.), though as long as the default dep, etc. worked, I'm personally just looking for semverLevel at the moment.

[raineorshine]

Okay, that's fair. A json object in the .ncurc would be a good place to specify these more advanced options.

[IlanFrumer]

+1

[raineorshine]

Closing with the revive-me tag for interested contributors. See #484.