node_modules in zero-installs monorepo with yarn workspaces. To commit or not to commit?

[DaviDevMod]

I created a monorepo with yarn workspaces using the most recent stable release, currently 3.2.0, which defaults to a zero-installs configuration. The automatically generated .gitignore looks like this:

.yarn/*
!.yarn/patches
!.yarn/plugins
!.yarn/releases
!.yarn/sdks
!.yarn/versions

# Swap the comments on the following lines if you don't wish to use zero-installs
# Documentation here: https://yarnpkg.com/features/zero-installs
!.yarn/cache
#.pnp.*

There's no node_modules and I guess it's because dependencies are packed and stored in .yarn/cache. However after installing dependencies in a workspace I get a quite populated node_modules at the root of the monorepo, which looks like the good ol' npm node_modules. Is it supposed to be committed?

Steps to reproduce:

Enable Corepack if you haven't yet:

corepack enable

Create the monorepo with yarn up to date and its zero-install workspaces.

mkdir temp-yarn-monorepo

cd temp-yarn-monorepo

yarn set version stable

yarn init -w

Add a workspace.

mkdir -p packages/my-package && echo '{"name": "my-package","version": "1.0.0"}' >> packages/my-package/package.json

Install microbundle in the workspace.

yarn workspace my-package add -D microbundle

Now you should be able to see a big, fat, tracked node_modules at the root of the monorepo.

Furthermore once I build my-package, a node_modules appears even in packages/my-package, though this one contains just a small .cache folder and I guess it's supposed to be committed, but I'm not sure.

[DaviDevMod]

It looks like the problem was that at some time I run yarn set version stable (or something similar) from the root of my machine. So it was like my entire laptop was a yarn monorepo, and I also found that it had the nodeLinker set to node-modules, which probably was the cause of the node_modules I was getting.