fastify-dx
unocss
fastify-dx | unocss | |
---|---|---|
23 | 56 | |
924 | 15,442 | |
- | 1.5% | |
0.0 | 9.7 | |
5 months ago | 6 days ago | |
JavaScript | TypeScript | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fastify-dx
-
Fastify GraphQL API Stack: with Mercurius & Nexus
Fastify DX is in the pipeline. It brings Vite-powered front end solutions in Svelte, React and other frameworks to Fastify and is already in alpha. This will let you create full stack apps using Fastify together with your preferred frontend.
-
Ask HN: What are the best GitHub READMEs you've seen?
The table layout and example formatting of "The Universal Route Module API Specification" is quite good: https://github.com/fastify/fastify-dx/blob/main/URMA.md
-
Fastify DX and SolidJS in the Real World
SolidJS ranked #1 in the 2021 "State of JS Front-End Frameworks", so we wanted to see what the fuzz is about and give it a proper chance with a side project. We started with a simple Single Page Application (SPA) and a few components but wanted to add data with GraphQL. For GraphQL we needed some sort of authentication, to identify users. This quickly turned more complex day by day. The biggest pitfalls and challenges were understanding Reactivity in SolidJS and the use of context providers. Last but not least, we wanted to add some server-side rendering capabilities, which lead to a three week rabbit hole of reading SolidJS code, Fastify Vite and lots of trial and error. Fortunately, Jonas Galvez was already working on Fastify DX a new full stack framework based on Fastify and Vite, where he added support for SolidJS as well. A nice side effect was that we not only have server-side rendering, but also async rendering, streaming web components/html streaming1 available, which is pretty awesome. As most of this is new and a lot of those technologies are barely documented past "Hello World" or "Todo List", we decided to extract the most important/difficult parts of our project into this "Real World Application with SolidJS and Fastify DX".
-
Hacker News top posts: Jul 12, 2022
Show HN: Fastify DX, a full stack framework based on Fastify and Vite\ (0 comments)
- Show HN: Fastify DX, a full stack framework based on Fastify and Vite
- Fastify DX: Full Stack Framework Built on Top of Fastify and Vite
- Fastify DX for Solid
unocss
-
Tailwind CSS v4.0.0 Alpha
I wish tailwind would support attributify like https://github.com/unocss/unocss, which is much more readable for complex layouts:
link
- UnoCSS — an Instant On-Demand Atomic CSS Engine
-
Catalyst – Tailwind CSS Application UI Kit
I feel the same about people praising Tailwind.
Tailwind (and similar, I tend to use https://unocss.dev/) is not good for your frontend architecture BUT they allow you to be so fast, that it negates the benefits.
For a job well done, I'd follow the principles of https://maintainablecss.com/
-
What do you think we can do better to improve Vue position in the frontend space as a dominant UI framework?
I think UnoCss is may be better than Tailwind already and has a good Vue integration https://unocss.dev/
-
~~New~~ Old way to write CSS
The most popular tools that implement this approach are: Tailwind, WindiCSS, UnoCSS.
-
Which is best for DX and efficiency, TailwindCSS, UnoCSS, PandaCSS, or the new MasterCSS
- UnoCSS: https://unocss.dev/
-
A design system for the federal government
haha, fair point. Still, I'm on the fence about how utility components are namespaced in USWDS. Perhaps giving users the flexibility to define the namespace might work better? One thing that bugs me is the absence of class-sorting like we have in TailwindCSS. Plus, there are some gaps I've noticed in USWDS. The naming, especially when comparing "padding-x-2" and "p-x-2", can be really annoying when switching around, maybe that could also be an option for the developer or project. Similar to the ideas antfu has on uno.css https://unocss.dev/ ♥
-
Modern CSS Framework or Library for Static Websites?
UnoCSS is a popular option
-
Vrite Editor: Open-Source WYSIWYG Markdown Editor
UnoCSS — for styling with Tailwind-like atomic CSS;
-
Why I Switched From Neovim to VSCode
Some exceptional libraries and frameworks only support VSCode, which you could argue is a bad thing, but it makes sense, VSCode is the most popular code editor after all. For example UnoCSS only has a VSCode extension, and it's my favourite way to write CSS. Astro has a LSP but I've found that the experience in VSCode is much better than in Neovim.
What are some alternatives?
astro - The web framework for content-driven websites. ⭐️ Star to support our work!
Tailwind CSS - A utility-first CSS framework for rapid UI development.
fastify-vite - Fastify plugin for Vite integration.
windicss - Next generation utility-first CSS framework.
vite-ssr - Use Vite for server side rendering in Node
tail-kit - Tail-kit is a free and open source components and templates kit fully coded with Tailwind css 3.0.
developers
unplugin-vue-components - 📲 On-demand components auto importing for Vue
fastify-dx-solidjs-example - Real world app using Fastify-DX, Solid.js, Auth0 and GraphQL
Quasar Framework - Quasar Framework - Build high-performance VueJS user interfaces in record time
solid-router - A universal router for Solid inspired by Ember and React Router
vanilla-extract - Zero-runtime Stylesheets-in-TypeScript