Problems with npm link'd dependencies #1167
Replies: 3 comments
-
I'm facing exactly this problem. This is my project and the output of
As you can probably guess, The only thing that effectively rebuilds my code is It'd be great to have a idiot-proof tutorial to get |
Beta Was this translation helpful? Give feedback.
-
Facing the same problem... The only thing worked for me so far is
|
Beta Was this translation helpful? Give feedback.
-
Precisely. This is the only thing that works as far as I can tell. There's a pending pull request to fix the issue properly in #2091. I've been using that without any problems. Maybe it will be merged in soon? As to why this happened, see #429 (comment) and the issue created to track this which #2088. |
Beta Was this translation helpful? Give feedback.
-
I have some issues when using
npm link
from another module into a project usingsnowpack
. When I change some code in the linked module,snowpack
notices some change but the linked module is not rebuilt.I tried instead to modify files directly under
node_modules/
folder, butsnowpack
doesn't notice any changes (I know now after chatting with @fks, that this is normal, just adding it to the conversation).When modifying the linked module, I don't see a
File changed...
event. But I notice that the browser page reloads. This is what I meant by some change above.Something else that I've noticed is that
snowpack
picks up the same kind of change when doing git operations, like commiting something. For example say I do something liketouch foo
or even stage the file by doinggit add foo
, then the browser reloads. Maybe not related at all, but just something that I noticed. It seems to me thatsnowpack
somehow notices changes in the corresponding.git/
folder.Beta Was this translation helpful? Give feedback.
All reactions