Nuxt-3 build crashes when using pinia

[lazercaveman]

Builds generated from Nuxt currently crashes (nuxt instance unavailable), whereas Nuxt can be run via dev without problems - anyways, the problem seems to be related to Pinia:

[nuxt] [request error] [unhandled] [500] Cannot find module '/Volumes/nuxt/.output/server/node_modules/pinia/dist/pinia' imported from /Volumes/nuxt/.output/server/chunks/page.mjs
  at new NodeError (internal/errors.js:322:7)  
  at finalizeResolution (internal/modules/esm/resolve.js:318:11)  
  at moduleResolve (internal/modules/esm/resolve.js:776:10)  
  at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:887:11)  
  at Loader.resolve (internal/modules/esm/loader.js:89:40)  
  at Loader.getModuleJob (internal/modules/esm/loader.js:242:28)  
  at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:76:40)  
  at link (internal/modules/esm/module_job.js:75:36)

After removing pinia entirely Nuxt works just fine - I don't know where the problem exactly is located - setup seems fine to me:

// Package.json

"dependencies": {
    "@pinia/nuxt": "^0.4.1",
    "pinia": "^2.0.21"
  }

// nuxt.config.ts

modules: ['@pinia/nuxt'],

// store

import { defineStore } from 'pinia';

export const useNavigationStore = defineStore('navigationStore', {
  state: (): {
    seoRoutes: object,
    routeReferences: routeReferenceType,
  } => ({
    seoRoutes: {},
    routeReferences: {},
  }),
  getters: {
    getSeoRoutes: state => state.seoRoutes,
    getRouteReferences: state => state.routeReferences,
  },
  actions: {
    setSeoRoutes (seoRoutes: object) {
      this.seoRoutes = seoRoutes;
    },
    setRouteReferences (routeReferences: routeReferenceType) {
      this.routeReferences = routeReferences;
    },
  },
});

[danielroe]

Would you try adding pinia to build.transpile?

[lazercaveman]

adding pinia was what i tried first, which resulted in the same outcome:

[nuxt] [request error] [unhandled] [500] [🍍]: getActivePinia was called with no active Pinia. Did you forget to install pinia?
        const pinia = createPinia()
        app.use(pinia)
This will fail in production.
  at useStore (./node_modules/pinia/dist/pinia.mjs:1681:19)  
  at setSeoRoutes (./.nuxt/dev/index.mjs:1010:3)  
  at page (./.nuxt/dev/index.mjs:1022:5)  
  at processTicksAndRejections (internal/process/task_queues.js:95:5)  
  at async ./node_modules/h3/dist/index.mjs:493:19  
  at async nodeHandler (./node_modules/h3/dist/index.mjs:439:7)  
  at async ufetch (./node_modules/unenv/runtime/fetch/index.mjs:9:17)  
  at async $fetchRaw2 (./node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20)  
  at async setup (./.nuxt/dist/server/server.mjs:5598:33)

Or did you mean pinia instead of @pinia/nuxt in general? : )

[danielroe]

Happy to look at it if you have a minimal reproduction.

[lazercaveman]

Thank you, I was hoping it is a known bug or problem, that I only did not found any infos to - there isn't really more that I could tell about using pinia within the project ... since I am currently not really using pinia within the project (just wanted to). I will try to setup a stackblitz project to reproduce and hopefully come back with some more information. : )

[lazercaveman]

Hello @danielroe, I setted everything up within stackblitz from scratch: https://stackblitz.com/edit/nuxt-starter-2cyqru?file=README.md

Same behavior, same problem - in dev everything is working as it should, when generating a build nuxt crashes.

[lazercaveman]

I have now experimented a bit and (among other things) cloned the example repo: https://github.com/piniajs/example-nuxt-3 and found that the problem also occurs here, as soon as I use Pinia in the server/api folder, the build crashes. Maybe it isn't thought to be used that way?

...The documentation seems to be a little vague about using pinia with SSR in Nuxt. : S

[maicss]

Same here

[lazercaveman]

The Feature seems not to be implemented - which is why it isn't working:
https://github.com/nuxt/framework/issues/7910

[maicss]

@posva #1587 Is this not a bug?

[lazercaveman]

No its not a feature ...