You must start pinia in a separate file and import it.
This is an example

./stores/index.ts

`import { createPinia } from 'pinia';

export const pinia = createPinia();`

app.ts

`...
import { pinia } from './stores';
...

const app = createApp(App);
app.use(pinia)`

Same result. You are just abstracting the variable. That will not have a different result.

createPinia() will always return type Pinia

They talk about server mode in replies. I don't know if it helps.

https://stackoverflow.com/questions/77913735/argument-of-type-pinia-is-not-assignable-to-parameter-of-type-plugin

I'm using it in my app.ts and no errors here, please post package.json to compare versions, mine is at "pinia": "2.1.7", right now - haven't updated it yet.

"pinia": "2.0.36"

"nativescript-vue": "3.0.0-rc.2",
"ts-loader": "^9.5.1",
"typescript": "^5.5.4",
"eslint": "^9.9.1",
"eslint-config-prettier": "^9.1.0",
"eslint-plugin-prettier": "^5.2.1",
"eslint-plugin-vue": "^9.27.0",
"@nativescript/android": "~8.7.0",
"@nativescript/eslint-plugin": "^0.0.4",
"@nativescript/ios": "~8.7.2",
"@nativescript-dom/core-types": "^1.0.29",
"@nativescript-dom/vue-types": "^1.0.15",
"tns-platform-declarations": "^6.5.15",

Upgrading everything fixed the issue.

Closing as the issue is outdated

So, I have one branch that is working. Another branch with all deps updated. I can not point out which package is breaking. Initially thought it was @vue/typescript-plugin that gave me this error after upgrading just a little.

but then there is this warning during pnpm install:

 WARN  Issues with peer dependencies found
.
└─┬ pinia 2.1.7
  └── ✕ unmet peer vue@"^2.6.14 || ^3.3.0": found 3.2.41

#10623

This issue happened when i upgraded and removed pnpm-lock.yaml