Build components that depend on pinia in library mode

[leopsidom]

I'm trying to build a component that depend on pinia to a npm package so I can import from another application. However currently I'm getting this error:

getActivePinia was called with no active Pinia. Did you forget to install pinia?
const pinia = createPinia()
app.use(pinia)

Even though I have already installed pinia in my main application.

Is this the expected behavior ? Though I have a feeling it might not be a good practice to include pinia or states into a library, I wanted to check if anyone else has encountered this problem.

[Nerderer]

Did you solve this?

We have the same issue, where we have component library (that uses Pinia) and a main application that consumes the components (this application is also using Pinia).

I can make it work by passing the active Pinia instance into an initialize components function that we use, then use setActivePinia(pinia) here. But I get this warning in the log:

[Vue warn]: injection "Symbol(pinia)" not found.

[krckyboy]

Bump.

[posva]

Make sure to:

• externalise pinia from the lib build
• Use one single pinia in the application

[mrichardsonjr]

"externalise pinia from the lib build" -- finally fixed the issue that's been driving me nuts.
God bless you, @posva

[botmaster]

Hello,
Not sure I understand. How to externalise pinia ?

[posva]

it depends on what you use to bundle your lib. You should be able to find the exact option with the word "external" or "exclude". This is for tsup: https://tsup.egoist.dev/#excluding-packages. For vite, rollupOptions.external should do

[botmaster]

Ok thank you @posva !