vite-plugin-pages VS pinia

vite-plugin-pages, auto generates routes for Vue components in the src/pages directory.

References to compare with something at all: * https://github.com/samchon/typescript-json (input transformer) * https://github.com/trpc/trpc (state-of-the-art end-to-end api) * https://github.com/spa5k/fastify-file-routes * https://github.com/hannoeru/vite-plugin-pages (frontend file-based routing)

Its more natural fit / easier to use for blog site. https://github.com/hannoeru/vite-plugin-pages is good too

I'm not sure what Nuxt adds. The vite-plugin-pages, has removed the only usecase I had for nuxt.

The good news is that, similar needs have been solved in the vite community with https://github.com/hannoeru/vite-plugin-pages, we just need to port it to webpack and https://github.com/unjs/unplugin got our back.

Thanks! I'll maybe work on some vite plugin to make it work here too since there are plugins like https://github.com/hannoeru/vite-plugin-pages

Since official SolidJS starter template are vite-based we can easily use vite-plugin-pages to create automatic routing a.k.a file based routing with official solid-app-router package.

File-based routing

Pinia tab is a feature integrated with Pinia, allowing you to view the registered modules and their details.

pinia

If you like Vuex, you'll love Pinia (the new official Vue state management library). At least, I enjoyed recently migrating my personal app from Vuex to Pinia. Pinia is even simpler / more straightforward than Vuex (and even more so compared to Redux).

Related

const authMiddleware: Middleware = ({ pinia }) => { // !!! Important !!! // tell all the stores you are contacting // Pinia instance, otherwise you will have problems because Pinia will access the global object // https://github.com/vuejs/pinia/blob/8626aac0049243de231401a01fe20092eeaf279c/packages/pinia/src/store.ts#L870 if (!authStore(pinia).isAuth) { return { path:'/login', status: 401, } } }

When installing the "pinia" package via npm i pinia, I got a bunch of errors, similar to what's described here. This seems to be an issue with npm. Solution to that : install using yarn add -D pinia

Does using the main branch of pinia fix your issue? Over aggressive unwrapping was changed in https://github.com/vuejs/pinia/pull/1444

Also, I tried one syntax based on : https://github.com/vuejs/pinia/discussions/1096