In the future, if a maintainer is running module-lint against a Yarn Classic project and they do not want to upgrade to Yarn Modern, they should be able to disable all of the Yarn-related rules (which are only concerned with Modern). However, if they do this but they have not disabled allow-scripts-related rules, then we still want module-lint to confirm that they've configured Yarn Classic to disable post-install scripts. However, currently, the package-allow-scripts-yarn-conforms rule only checks the Yarn Modern config file — it does not care about Yarn Classic. We may want to add a new version of this rule which checks the Yarn Classic config file.
In the future, if a maintainer is running
module-lintagainst a Yarn Classic project and they do not want to upgrade to Yarn Modern, they should be able to disable all of the Yarn-related rules (which are only concerned with Modern). However, if they do this but they have not disabledallow-scripts-related rules, then we still wantmodule-lintto confirm that they've configured Yarn Classic to disable post-install scripts. However, currently, thepackage-allow-scripts-yarn-conformsrule only checks the Yarn Modern config file — it does not care about Yarn Classic. We may want to add a new version of this rule which checks the Yarn Classic config file.