My understanding is that caching the

node_modules

directory can have unintended consequences if the architecture/OS/OS version changes, because some packages build native libraries and they may not get rebuilt correctly.

setup-node

uses

cache

internally, but caches the cache dirs in the user's home directory and does

hashFiles()

on all the

package-lock.json

files it finds in the tree