Should I commit /.nx directory into the version control?

[HesamSe]

In the recent versions of nx, the .nx directory was added to the project root. It contains only a cache directory but I think more things will be added.
Should I add it to git?
If yes, What is the benefit of that?
Is it a good practice to add caches to version control? As you know, git is not optimized for dealing with large files.

[FreekVanDooren]

Thanks for posting this question. I'm adding .nx/cache to .gitignore for the time being as I feel local caches shouldn't be version controlled and it looks like there is a remote caching-feature which I guess is preferred/recommended. We're not using it (yet 🤷)

[AgentEnder]

.nx/cache and .nx/installation should be gitignored. I'd refrain from ignoring the whole directory as more stuff may be added that would make sense to keep there.

[Ben-Barron]

How about .nx/workspace-data/d
Looks like to info about/logs for the daemon, the files for which are referenced in .nx/workspace-data/file-map.json

[AgentEnder]

.nx/workspace-data should be gitignored

[scott-gmr]

This makes it hard to know what to actually do about this directory. We're supposed to not commit certain subdirectories of this, but only one of those was actually added to my .gitignore by nx migrate. I'm not sure what to trust then. The main pain I have with Nx are these types of inconsistencies that make maintaining a repository in this awkward place where I both am expected to trust Nx CLI to "take care of things" but then can't actually do that and have to get in the weeds with all sorts of configuration files and learn that I've been committing directories I never should have been in the first place, because it seemed that I should have just been trusting the CLI that explicitly updated my .gitignore.

[AgentEnder]

This makes it hard to know what to actually do about this directory. We're supposed to not commit certain subdirectories of this, but only one of those was actually added to my .gitignore by nx migrate. I'm not sure what to trust then. The main pain I have with Nx are these types of inconsistencies that make maintaining a repository in this awkward place where I both am expected to trust Nx CLI to "take care of things" but then can't actually do that and have to get in the weeds with all sorts of configuration files and learn that I've been committing directories I never should have been in the first place, because it seemed that I should have just been trusting the CLI that explicitly updated my .gitignore.

There should be migrations for both the .nx/cache and .nx/workspace-data directories, if there is a case where that didn't get migrated it'd be appropriate to open a bug report