trackunit/eslint-plugin-trackunit v0.8.0 - rules that used to warn are now errors
Breaking change if your workspace uses @trackunit/eslint-plugin-trackunit: from v0.8.0, the base and react presets no longer set any rule to warn. Rules that used to report as warnings now report as errors, so npx nx run-many -t lint can start failing on code that previously only printed a warning.
Affected rules
@trackunit/no-typescript-assertion, @trackunit/no-deprecated-graphql-fields,
@typescript-eslint/strict-boolean-expressions, @typescript-eslint/no-non-null-assertion,
@typescript-eslint/await-thenable, @typescript-eslint/ban-ts-comment,
@typescript-eslint/no-require-imports, import-x/no-default-export,
no-restricted-syntax (enums), react/no-unstable-nested-components,
react/jsx-no-constructed-context-values, react-hooks/refs, react-hooks/set-state-in-effect,
react-hooks/preserve-manual-memoization, react-hooks/incompatible-library,
testing-library/no-debugging-utils
What to do
After upgrading past v0.8.0 (check your version with npm view @trackunit/eslint-plugin-trackunit version or by reading your package-lock.json), run:
npx nx run-many -t lint
Fix any new errors, or turn a specific rule back down for a project:
libs/[feature-name]/[name-of-your-extension]/eslint.config.cjs
module.exports = [
...require('../../../eslint.config.cjs'),
{
files: ['**/*.ts', '**/*.tsx'],
rules: {
'@typescript-eslint/strict-boolean-expressions': 'warn',
},
},
];
See Linting for the full override pattern and Keep the plugin up to date for how the plugin version tracks your other @trackunit/* upgrades.