-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
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
feat(core): allow using project patterns rather than just project names with nx watch
#16768
feat(core): allow using project patterns rather than just project names with nx watch
#16768
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
74cfb96
to
8e2d244
Compare
8e2d244
to
df0a9b8
Compare
df0a9b8
to
837455f
Compare
837455f
to
a83deac
Compare
…es with `nx watch`
a83deac
to
0555f3b
Compare
packages/nx/src/daemon/server/file-watching/file-watcher-sockets.ts
Outdated
Show resolved
Hide resolved
Hello @AgentEnder, which version should that be part of? Don't see it in the release notes and it also doesn't work for me with 16.1.3. Thanks |
Its not released yet, but should be part of 16.2.0 whenever it lands |
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
nx watch
accepts a list of project names via--projects
, but doesn't usefindMatchingProjects
and thus has inconsistencies with run-many, affected (--exclude), implicitDependencies, dependsOn, and inputsExpected Behavior
All
projects
fields usefindMatchingProjects
Related Issue(s)
Fixes #16761