React VS Tailwind CSS

React because it’s a widely popular front end library

Vite Documentation Next.js Documentation React Docs

Source: React.js Github

🔵 React

Metadata is huge - One may expect package metadata to be smaller than package contents. The results show, that exactly the opposite is true with package content size being about 53 MB, while package metadata size being about 77 MB (or 81 MB for Nexus). This should be no surprise since metadata contains all package versions, which can easily be more than a thousand as evidenced above for the react package.

React Documentation: https://react.dev/

I first tried to use growthbook. They had only react support. I thought - I could use the js sdk and work around it. Ok fine. It seemed a bit complicated to use in terms of their UI. Okay fine, I try to find an easier one maybe I can self-host. That way I could even put it behind cloudflare CDN and use caching on it and clever cache-busting when I change values could help propagate changes. Okay fine I have a plan. I ended up going with Flagsmith instead. It was even easier. Perfect.

As far as I'm aware, TC39 hasn't yet specified which shape of literal is "ok" and which one is "wrong" to run on a computer, depending on wether this computer has a screen or not. I imagine this is why V8, JSC and SpiderMonkey let you create objects of any shape you want on any environment. I don't understand what's wrong about using this shape on the server.

[1] https://github.com/facebook/react/blob/e71d4205aed6c41b88e36...

A basic knowledge of React is required. Strapi plugins are developed using React.js.

Yup provides you with a declarative way to validate form data in JavaScript apps. It has a set of features which make it a flexible and efficient choice for handling validation in React, React hook form, and other frameworks.

TailwindCSS

shadcn/ui contains a set of beautifully designed and accessible components, and it works seamlessly with major React frameworks. It’s open-source and has amassed 85.5k (and counting) GitHub stars. It’s built on the shoulders of giants — Radix UI and Tailwind CSS, making it one of the best to work with. Unlike many other UI libraries, the components are not just installed as npm modules, they’re downloaded into your project. That gives you access to the source code and you can modify it if you want. I like this approach better because I can tweak aspects of a component if I want to.

We're going to investigate the difference in performance between Tailwind and Linaria. Tailwind, you already know. And Linaria has been getting quite a lot of traction since styled components went into maintenance mode recently. We'll cover why Linaria is a good choice for this comparison a bit further.

Styling: Tailwind CSS

Requesting RISC-V support upstream (see: Tailwind GitHub issue)

It is a well-known fact that Tailwind CSS is a utility-first CSS framework. It lets you style elements directly within your HTML, thanks to pre-defined classes. Unlike other CSS frameworks that offer pre-built components, Tailwind offers these low-level utility classes that let you create your own design system. Thus, this makes crafting unique responsive designs effortless as there is not much to do with custom CSS.

live/tailwind starts tailwind on watch mode. Notice the watch=always flag, there seems to be an issue with tailwind closing when stdin closes and this flag fixes it. (related pr)