feat(cooldown): support for cooldown predicate function

[SebastianSedzik]

Description

This PR adds support for passing a predicate function to the cooldown option, providing more granular (per-package) control over cooldown behavior — for example, setting different cooldown durations or disabling cooldowns for specific packages (see example below).

Docs

You can also provide a custom function in your .ncurc.js file or when importing npm-check-updates as a module.

⚠️ The predicate function is only available in .ncurc.js or when importing npm-check-updates as a module, not on the command line. To convert a JSON config to a JS config, follow the instructions at https://github.com/raineorshine/npm-check-updates#config-functions.

/** Set cooldown to 3 days but skip it for `@my-company` packages.
  @param packageName     The name of the dependency.
  @returns               Cooldown days restriction for given package.
*/
cooldown: packageName => packageName.startsWith('@my-company') ? 0 : 3

Resolves: #1562

[raineorshine]

Thanks! This looks great.

[raineorshine]

This doesn't seem right that the packageFile was removed. Can you explain?

[SebastianSedzik]

@raineorshine Yes, this is intentional. I removed the test/test-data/cooldown/package.json file in an earlier PR but missed the references in these two tests. Since both are designed to fail during options type checking, NCU never reaches the code that loads or checks the package path. The issue only became visible when I temporarily broke the options checker during development. Keeping the packageFile option in these tests could be misleading, as the referenced file no longer exists.

[raineorshine]

I see! Thanks for clarifying!

[raineorshine]

I see! Thanks for clarifying!