What is the current behavior?
I was using NPM link just fine, and then the dependency I was NPM linking needed a little debugging of its own, and I linked two other modules to that module’s directory.
Then I tried to run
npm run start from my create-react-app and I got this error below.
I then tried to unlink those two extra links to my originally linked module, but that has done nothing.
Now even though I have the same setup that I had before - just one link from my create-react-app app to my linked module - I get . this error every time, whenever anything is linked at all. I even get it after removing the previous folder, unlinking everything, creating the same dependency in a new folder and linking that.
Here’s the error:
If the current behavior is a bug, please provide the steps to reproduce.
NPM link one module, then npm link that module to a couple other modules, and try to run npm run start from a create-react-app app.
Unlink all those modules and just link the first one once. See the messed up stuff.
I am on a Macbook Pro from 2017.
What is the expected behavior?
Expected successful behavior without bug? I can simply use my npm linked module. Bonus: I can use my npm linked module with that module linked to a couple other modules so I can debug multiple modules quickly.
Other relevant information:
webpack version: 4.29.6
Node.js version: 11.12.0
Operating System: MocOS Mojave 10.14.4
Additional tools: NPM 6.7.0