Important
Since Nx 18 introduced inferred targets, we made some changes to try and introduce compatibility with this in the last version of the plugin.
However, an issue with Nx 19 is that there is now a determination process for which target to use (explicit target -> inferred target -> npm script).
Since we removed the function generator lint target (using only what @nx/node:app gives us) but left the lint npm script in place, an infinite loop occurred - nx lint infers lint npm script -> which runs nx lint
To remedy this and to save me from existential hell with this plugin, I've decided to keep a lint target in the project.json files the plugin creates. This is the simplest and most widely compatible solution.
Otherwise we'd have to consider if user workspaces are using inferred plugins for lint, if they're using project.json files, if they're using nx configs in package.json, if they're wanting to use npm scripts... it compounds horribly.
So this is the pragmatic approach we've taken.
Note
Nx 19 warns that --projectNameAndRootFormat will be removed in Nx 20.
We'll address that problem in the next plugin version update.
What's Changed
- feat: Update to Nx 19.8.14 by @simondotm in #258
- Bump version to 19.8.14 by @simondotm in #259
Full Changelog: v18.3.5...v19.8.14