Replies: 3 comments 6 replies
-
Any chance you found a solution for this in the past year? |
Beta Was this translation helpful? Give feedback.
-
Interesting, I have a similar setup without the issue. Only difference is instead of npm link, I'm just doing an import through the file system like: In the library I go tsc --watch, and most changes reflect right away (except types, which I think might be because --watch might not be emitting them, would have to check). |
Beta Was this translation helpful? Give feedback.
-
This is still an issue. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Run
next info
(available from version 12.0.8 and up)No response
What version of Next.js are you using?
12.0.7
What version of Node.js are you using?
17.3.0
What browser are you using?
Vivaldi
What operating system are you using?
Linux
How are you deploying your application?
next dev
Describe the Bug
Hey,
I'm developing a library for nextjs which includes some api functions and also some ui components (react).
For testing purposes I have a nextjs project where i'm linking this library via
yarn link
.Unfortunately changes in the library don't trigger a recompilation of eg. a page where I'm using one of the components (it's .
Neither the HMR nor a manual reload will show the new changes. Actually I have to stop the
next dev
process, remove the.next
folder and startnext dev
again.I don't know if it's a setting in webpack / swc / next. Is there a build cache or something I can disable?
Expected Behavior
Changes in node_modules should reflect in compiled pages.
To Reproduce
Beta Was this translation helpful? Give feedback.
All reactions