Switching to the yarn zero installs approach (see

CodePudding user response：

As per comments, it turns out that another ignore rule was overriding the desired un-ignore rule. The key diagnostic was to use:

git check-ignore -v .yarn/unplugged/somedir/node_modules/somefile

(or similar), which pointed to the **/node_modules/ line that caused somefile within this node_modules/ within .yarn/unplugged/ to be skipped.

The more general takeaway here is that if git add . is skipping some file(s), you can use often use git check-ignore -v to find out why. Note that it's important to use it on a particular skipped file. (It also doesn't do very much good with submodules, but that's another problem entirely.)