Problem
Currently, fallow doesn't have a configuration to mark a dependency as always available, which can lead to known good dependencies being marked as unlisted.
A very easy example of this is bun: modules.
Proposed solution
Treat ignoreDependencies listed deps as both "always considered used" as well as "always considered available".
Alternatives considered
I see three alternative ways to approaching this:
- Add
bun: to a 'hard-coded' list of known goods, in the same way as node:.
- Allow for a rule specific configuration (
rules.unlistedDependencies.ignoreDependencies) object which serves as ignore.
- Add a new configuration key "globalDependencies" or similar, for dependencies which aren't listed in the package but are known available in actual use.
Problem
Currently, fallow doesn't have a configuration to mark a dependency as always available, which can lead to known good dependencies being marked as unlisted.
A very easy example of this is
bun:modules.Proposed solution
Treat
ignoreDependencieslisted deps as both "always considered used" as well as "always considered available".Alternatives considered
I see three alternative ways to approaching this:
bun:to a 'hard-coded' list of known goods, in the same way asnode:.rules.unlistedDependencies.ignoreDependencies) object which serves as ignore.