phero VS vite-plugin-pages

That's one of the reasons that drove me to create Phero: https://phero.dev

I’m one of the authors of Phero. It’s goal is similar to tRPC: fullstack typesafety between servers and clients.

One difference is syntax: Phero leverages the TS compiler api to generate parsers for your backend functions. It will parse input and output or your api, automatically, based on the types you define for your functions. It will generate a declaration file of your api and generate an RPC style client SDK for your frontend. Another difference is that it aims to be more batteries includes.

[1] https://github.com/phero-hq/phero

Comparison: https://phero.dev/docs/comparisons/tRPC

Shameless plug: you could also use https://phero.dev

Long story short: when fetching data, you should be validating the data, before casting it to a type you’re expecting it to be. There are a lot of different approaches for this, but being the go-author my favorite would be Phero (https://phero.dev). With this, you can build your API in typescript as well, automatically generate a client for your frontend to call the API. Phero will make sure all data is correct in runtime, automatically.

For those looking for an alternative: Definitely check out https://phero.dev. As the co-creator I’m totally biased of course, but thanks to its build-step IDE-performance is great 😊👍

What about Phero? https://phero.dev

Can we add Phero to the list? :) https://github.com/phero-hq/phero

You can use Phero. You can use it on your backend and frontend. It basically created a typed API from your backend afaik

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