I must admit, I have never tried that.
I first started developing with NodeJS using Linux, so symlinks just felt as a natural tool. I symlinked the packages manually in the beginning, until I came across
npm link. When we started developing NodeJS at work using Windows, I just kept that approach.
There are some advantages to this approach:
- the workspace is relocatable, because the links always point to the location of your global npm package directory
- you can just "install" it using its package name, no need to know the path to the package
That makes it easier for setup scripts (e.g. for a VSCode workspace) to get everything up and running.
But I will surely give it a try. Maybe it works with relative paths, too.