fix: Fixes typing in Store when connecting

[avil13]

Description

When pinia-plugin-persistedstate is connected - stor types are broken.

The problem is that the type used is not imported.

This PR fixes this error.

[avil13]

@prazdevs Hi. Do you have the ability to accept the PR?

[agross]

@prazdevs Please have a look, this is affecting our project as well.

[prazdevs]

That's rather odd because the type doesn't need to be imported as its used inside declare module 'pinia' which has Store.
Could you provide a repo where you reproduce the error ?

[avil13]

@prazdevs

This error is reproduced on large projects, it looks like TS is failing.

Is there any reason why the Store dependency was removed from pinia imports?

[prazdevs]

It has never been added to my knowledge. We're redeclaring the module (pinia) so Typescript will look up for types in said module. If you add the import, TS tells you it's unused 🤔

[avil13]

This is an ESLint warning, not TS

[prazdevs]

This is an ESLint warning, not TS

well there's also a ts warning above the eslint one 😅

[prazdevs]

Closing this without a proper issue / reproduction repo where the error occurs 😥

[agross]

I only got around to trying to create a repro today. I started with our project's source code and removed code until there was no error running npm run type-check.

This is the repro: https://github.com/agross/pinia-repro

Please reopen here accordingly. To "fix" the error, run rm src/components/__tests__/ComponentUsingStore.spec.ts. I don't know why removing that file/test fixes the type errors. VS Code certainly doesn't show any for the auth.ts file, and npm run test:unit succeeds.

[avil13]

@agross Thanks for the tip on how to look for the problem.

I have found what the cause is.

TS is trying to optimize AST. So it is not loading data that is not being used right now.

To load the extension type, you can do an import from a package that extends pinia.

@prazdevs reopen the current PR and I will add a fix.