vite-plugin-pages VS windicss

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

why not use Windi CSS or Tailwind css?

Windi CSS, in contrast to Tachyons, is a very fresh framework. Started in the late December of 2020, it’s already gained a lot of attention and currently sits at respectable 1.5K GitHub stars.

No mention of Windi CSS? Didn't it inspire this?

However I decided it was time to question my own biases. I installed Tailwind Intellisense for VS Code and started up a test project with a starter that included Tailwind (actually it uses Windi, which is a Tailwind compiler). I then started making a basic site, forcing myself to use the utility classes for (most) all of the styling.

For more details, please check windicss

You can check the README of windicss (https://github.com/voorjaar/windicss). Compared with postcss, it runs faster, can be built in real time and does not require plugins such as autoprefixer and purgecss to increase the complexity of configuration. And windicss extends the utilities and variants of tailwindcss. For example, you can directly use p-1.3rem or bg-hex-fff just like atomic css. And we also have a compilation mode, which can combine a line of classes into one to increase the readability of html.