This video really helped me, thanks for taking the time to make it. In my case it turned out that I was using a stale version of the library somehow, so my updates hadn't been incorporated into the web app, which is ultimately why it wasn't working. I changed the version number and noticed it wasn't increased in the node_modules folder. Going through your video helped me work that out. I liked your novel approach for checking the export matched.
thank you so much! Im sad to admit how long this took me ( 2 days ) thank you so much again! Also good advice, I do agree the more senior we get the more and more I just skim docs and it always ends up hurting me T-T
I have exactly the same issue. I'm trying to copme up with an easier solution for this. Does anyone have any idea how this linking process could be made easier?
Hi, I am having this issue and when I link the react version from my external package, it unlinks the actual package and vice versa. I’ve been running around in circles trying to fix this. Any help would be appreciated
From the package root directory, run "npm link ./path-to/app/node_modules/react. And then in the app root directory, run "npm link @mypackage/pkg". Are you linking multiple packages? If so make sure you link multiple package in the same command. For example, if you want to link @mypackage/pkg1 and @mypackage/pkg2, then make sure you run "npm link @mypackage/pkg1 @mypackage/pkg2" in the app root directory. Hope that helps :)
This video really helped me, thanks for taking the time to make it. In my case it turned out that I was using a stale version of the library somehow, so my updates hadn't been incorporated into the web app, which is ultimately why it wasn't working. I changed the version number and noticed it wasn't increased in the node_modules folder. Going through your video helped me work that out. I liked your novel approach for checking the export matched.
i did not understand where should i use npm link
Thanks for posting this, I had spent about 3 hours trying to solve this exact issue!
Yep, this solved the problem. I’m presenting the component library in 2 days & I‘ve been at my wit’s end I tell ya, you’ve saved my hide here buddy
thank you so much! Im sad to admit how long this took me ( 2 days ) thank you so much again! Also good advice, I do agree the more senior we get the more and more I just skim docs and it always ends up hurting me T-T
For this solution i have spent 2-3 days man thanks for this
I tried to solve this problem from 16 hours now I find the solution thanks brother 😊😊
Big thank you from Brazil my man!!!
Thank you, this was very helpful!
4 hours? Try 2 weeks lol. There's still something very inconsistent about this solution from react.
You just saved me 2 hours, thank you 😂
Thank you so much!
I have exactly the same issue. I'm trying to copme up with an easier solution for this. Does anyone have any idea how this linking process could be made easier?
Hi,
I am having this issue and when I link the react version from my external package, it unlinks the actual package and vice versa. I’ve been running around in circles trying to fix this. Any help would be appreciated
From the package root directory, run "npm link ./path-to/app/node_modules/react. And then in the app root directory, run "npm link @mypackage/pkg".
Are you linking multiple packages? If so make sure you link multiple package in the same command. For example, if you want to link @mypackage/pkg1 and @mypackage/pkg2, then make sure you run "npm link @mypackage/pkg1 @mypackage/pkg2" in the app root directory. Hope that helps :)
Thank YOU
This helped a lot bro ❤