You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using lint-staged with nx affected to lint fix a module, some files won't be staged because lint-staged only adds the files that were matched by the micromatch,
the command that I'm using is nx affected -t lint --files=${files} --fix, which means that all modules that those files affected will be linted and fixed, which might cause more files to be linted and fixed
Steps to reproduce
initialize NX workspace
use @nx/dependency-checks (which means when you use a new package in a module it would automatically add it to pakcage.json)
use a new package in a js file in the module
commit with lint staged
Debug Logs
No need
Environment
OS: Windows 11
Node.js: v20.14.0
lint-staged: ^15.2.10
The text was updated successfully, but these errors were encountered:
a fix would be add a new cli option (like --stage-all) which will stash all unstaged changes, then when the lint-staged tasks finish it will stage all new changes
Description
When using
lint-staged
with nx affected to lint fix a module, some files won't be staged becauselint-staged
only adds the files that were matched by the micromatch,the command that I'm using is
nx affected -t lint --files=${files} --fix
, which means that all modules that those files affected will be linted and fixed, which might cause more files to be linted and fixedSteps to reproduce
@nx/dependency-checks
(which means when you use a new package in a module it would automatically add it topakcage.json
)Debug Logs
No need
Environment
lint-staged
: ^15.2.10The text was updated successfully, but these errors were encountered: