We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NX fails to locate projects that are located inside directories that starts with a dot -- (.github, .config etc).
.github
.config
A command such as nx run .github:lint should run without issues.
nx run .github:lint
https://github.com/e-graveyard/nx-examples
npm i --legacy-peer-deps
npx nx run working:say-hello
project.json
tools
npx nx run not-working:say-hello
.circleci
> NX Report complete - copy this into the issue template Node : 20.5.1 OS : darwin-arm64 npm : 9.8.0 nx (global) : 16.6.0 nx : 16.7.1 @nx/js : 16.7.1 @nx/linter : 16.7.1 @nx/workspace : 16.7.1 @nx/devkit : 16.7.1 @nrwl/tao : 16.7.1 nx-cloud : 16.4.0-beta.1 typescript : 5.1.6
No response
This bug is not present on version 16.6.0 and older.
16.6.0
The text was updated successfully, but these errors were encountered:
.
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.
Sorry, something went wrong.
AgentEnder
Successfully merging a pull request may close this issue.
Current Behavior
NX fails to locate projects that are located inside directories that starts with a dot -- (
.github
,.config
etc).Expected Behavior
A command such as
nx run .github:lint
should run without issues.GitHub Repo
https://github.com/e-graveyard/nx-examples
Steps to Reproduce
npm i --legacy-peer-deps
)npx nx run working:say-hello
; it should run without problems (project.json
undertools
dir)npx nx run not-working:say-hello
; it should fail with a "not found" error (project.json
under.circleci
dir)Nx Report
Failure Logs
No response
Operating System
Additional Information
This bug is not present on version
16.6.0
and older.The text was updated successfully, but these errors were encountered: