PraZ
PraZ
I checked a bit and played with it. I like where this is going and it makes working with stores in middleware possible, however, I'm not sure this is the...
Ok so maybe we could just copy/paste the `pick` method to the nuxt plugin to avoid touching the base plugin at all while we work on the Nuxt thing. Later...
Ig it's fine using lodash-es in the Nuxt plugin, we'll see later what we can do. This issue has to be adressed so let's try things! I let you update...
nw take your time ^_^ lodash are working on a v5 with native typescript, usm exports so could be a good start to see what we can do with it...
I would see this as a breaking change because it changes the rehydration behaviour, but i totally see it as a feature/something needed. Maybe keep it being a flag as...
PRs are always welcome :) That being said, keep in mind the nuxt module is an implementation of the base plugin, to work easily with Nuxt, and for _most_ uses....
the provided repo gives me an error on install 🤔 ``` pnpm: /@akryum/[email protected] is an invalid relative dependency path at Object.parse2 [as parse] (C:\Users\praz\.node\corepack\pnpm\8.2.0\dist\pnpm.cjs:113619:15) at nameVerFromPkgSnapshot (C:\Users\praz\.node\corepack\pnpm\8.2.0\dist\pnpm.cjs:113728:28) at addPreferredVersionsFromLockfile (C:\Users\praz\.node\corepack\pnpm\8.2.0\dist\pnpm.cjs:186437:89)...
Ok, I have it working but have several concerns: 1. Why would pinia be needed for histoire components ? 2. Is the issue only with this particular pinia plugin ?...
My question was more "is there another plugin that can cause this" and i think there may be. For some reason, the config options just dont get passed 🤔
Hi, as a temporary workaround, you can disable the plugin for when the project is run by histoire with this ```ts export default defineNuxtConfig({ modules: [ // ... other modules...