Uncaught (in promise) Error: [🍍]: getActivePinia was called with no active Pinia. #886
Unanswered
sdoerger
asked this question in
Help and Questions
Replies: 1 comment 6 replies
-
This is because of how linking keeps relative dependencies, e.g. your linked library will keep its relative dependency to pinia, vue, etc while your app using the linked library will use its own relative dependency of pinia, vue, etc. And that will create problems when it comes to Personally, I use https://github.com/wclr/yalc to deal with this. |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there, again great library. Replaced Vuex with it in my project.
However, I created myself a helper class, because I created them (like 20) always in the same way.
Then I thought, that class would have been great, when I started out with Vue and that would be a great first npm package project for me too.
To test it, I used
npm link
in my project, which worked great, but if I install it withnpm install
I get that error ... why?As mentioned, first time that I created anything like that.
Any chance you can have a look at my repo?
It is just a single index file (because import form "./src/..." did not work)
Sorry if I waste time for very likely not properly at all, rushing in building a npm package. But if it is something kinda tiny or you can point me into the right direction, that would be really great.
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions