I use rules like prefer-caret-version-dependencies. However, sometimes a dependency has a problem that requires me to specify a version range that cannot be represented with a caret version.
Looking at the documentation, I cannot see a way currently to specify exceptions to the rule. Either all dependencies are checked and if any of them don't use the caret syntax, I get an error. Or I have to turn off the rule or make it a warning. But a warning is not really the level of forcefulness I want. It is too easy to miss a warning.
The text was updated successfully, but these errors were encountered:
@ntwb - I'm curious if you would prefer this for your monorepo scenario.
Use globs to specify different config for sub-packages (note the draft structure below is a breaking change. I'm not sure about this syntax 🤓. I'm curious where some for the RFCs for ESLint will go in 2019).
The linter would use the first config object for the root package.json file. The linter would use the second config object package.json files in the submodules directory.