Skip to content
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

Nx does not recomputes project graph afer changes in node_modules #27943

Open
4 tasks
Exelord opened this issue Sep 16, 2024 · 4 comments
Open
4 tasks

Nx does not recomputes project graph afer changes in node_modules #27943

Exelord opened this issue Sep 16, 2024 · 4 comments

Comments

@Exelord
Copy link

Exelord commented Sep 16, 2024

Current Behavior

When switching to a branch with yarn.lock changes, NX does not recomputes the graph automatically. After running yarn install I need to manually nx reset in order to get a correct graph and use remote cache.

Expected Behavior

When switching to a branch with yarn.lock changes, NX does recomputes the graph automatically and it is watching for any change in node_modules.

GitHub Repo

No response

Steps to Reproduce

  1. Switch to a different branch with changes in dependencies
  2. Try to get targets from remote cache [no cache]
  3. install dependencies and try again [ no cache ]
  4. run nx reset
  5. Try again running from cache [ remote cache found ]

Nx Report

NX 19.7.2

Failure Logs

No response

Package Manager Version

No response

Operating System

  • macOS
  • Linux
  • Windows
  • Other (Please specify)

Additional Information

No response

@jaysoo
Copy link
Member

jaysoo commented Sep 25, 2024

Do you have a repro that you can link to for us to debug?

Copy link

github-actions bot commented Oct 3, 2024

This issue has been automatically marked as stale because more information has not been provided within 7 days.
It will be closed in 21 days if no information is provided.
If information has been provided, please reply to keep it active.
Thanks for being a part of the Nx community! 🙏

@github-actions github-actions bot added the stale label Oct 3, 2024
@julianobrasil
Copy link
Contributor

It happens to me all the time. I basically got used to yarn nx reset whenever I switched branches.

@github-actions github-actions bot removed the stale label Oct 23, 2024
Copy link

This issue has been automatically marked as stale because more information has not been provided within 7 days.
It will be closed in 21 days if no information is provided.
If information has been provided, please reply to keep it active.
Thanks for being a part of the Nx community! 🙏

@github-actions github-actions bot added the stale label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants