compiled
PostCSS
compiled | PostCSS | |
---|---|---|
16 | 86 | |
1,962 | 28,221 | |
0.4% | 0.2% | |
9.0 | 8.8 | |
4 days ago | 10 days ago | |
TypeScript | TypeScript | |
Apache License 2.0 | 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.
compiled
-
Why is tailwind so hyped?
tags inside SFCs are typically injected as native
</code> tags during development to support hot updates. <strong>For production they can be extracted and merged into a single CSS file.</strong></p> </blockquote> <p>There are also 3rd party CSS libs that do the same thing such as <a href="https://linaria.dev/">linaria</a>, <a href="https://vanilla-extract.style/">vanilla-extract</a>, and <a href="https://compiledcssinjs.com/">compiled CSS</a>. Which can be used in the event you're stuck with something that doesn't have baked in support via SFC formats (looking at you React).</p> <p>These are my preferred ways of handing it.</p> <ol> <li>Tailwind</li> </ol> <p>Option 2 is tailwind, which works backwards.</p> <p>That is, instead of the above with extraction where you write the styles, and the framework or libs extract them and replace them with class names, it's the other way around.</p> <p>You're writing class names first (which are essentially aggregated CSS property-values) which then generate and/or reference styles.</p> <p>It has the advantage of being easy to write (assuming you've got editor LSP, linting, etc), but as you've discovered, it's difficult to read / can get really messy really fast.</p> <p>As far as all the other claims on the Tailwind site, it's all marketing, at least 80% bullshit.</p> </div>
- Individual css for every component?
-
Hey friendos, need some help choosing a "framework" with some specific requirements in mind
Your choice of CSS lib. Bootstrap can still be a valid choice, tho you may want to check the docs of whatever SSR / SSG framework you end up using as they may have better (or worse support). For example if you wanted to do CSS-in-JS (Next) i'd consider Linaria, vanilla-extract, or compiled.
-
Why We're Breaking Up with CSS-in-JS
So to be extremely clear, the issue isn't CSS-in-JS per se, it's just that the author only looked at implementations that don't generate create CSS files. He notably mentioned the (apparent) zero-runtime solutions Vanilla Extract and Linaria, only to skip them and complain that Compiled inserts nodes at runtime.
Compiled
-
How common is using styled components?
Link: https://compiledcssinjs.com/
-
SASS vs CSS Modules vs CSS-in-JS vs Compile time CSS-in-JS. Who wins?
Compiled (Compile time CSS-in-JS solution from Atlassian)
-
CSS in JS zero runtime libraries similar to JSS which allow to reuse styles?
Stitches Is near zero runtime and vanilla-extract claims it's zero runtime and typed. There's atlassian compiled as well but I never used it.
-
Goodbye CSS Modules, Hello TailwindCSS
Author here, I haven't had time to play around with it, but this library[0] from Atlassian looks like a "best of the both worlds" styling approach: CSS-in-JS authorship without the runtime penalty.
[0] https://compiledcssinjs.com/
- A familiar and performant compile time CSS-in-JS library for React
PostCSS
-
PostCSS - my initial experience
the plugins in the official PostCSS website were old like IE6 or the marquee tag, and
-
Dark Mode with SvelteKit, a Blog Post
Hello internet. I just published a new blog post on how to implement dark mode with SvelteKit, optionally with PostCSS and TailwindCSS:
-
11 Ways to Optimize Your Website
There are many frontend tools available for this purpose. For example, PostCSS is a popular CSS processor that can combine and minimize your code. With the right plugin, it can even fix your code for compatibility issues, making sure your CSS styles work for all browsers.
-
Styling React 2023 edition
I use PostCSS to extend CSS’s features and to add a few things that make writing styles a little more convenient, but it could easily be swapped for another preprocessor like Sass or vanilla CSS. It’s up to you. You can view my PostCSS config here.
-
Abstract Syntax Trees and Practical Applications in JavaScript
Code transpilation isn't specific to JavaScript, You can also add a level of transformation to your CSS source using tools like post-css. Most languages with a fairly mature ecosystem will probably have some tools to help with code transformation.
-
Native CSS nesting now supported by all major browsers!
In large projects, it is still a good idea to use PostCSS, which will translate new CSS features to something that browsers understand today.
- Unicode-range CSS is working wrong in Safari browser?
-
Let's Make Learning Frontend Great Again!
LiveCodes provides many of the commonly used developer tools. These include Monaco editor (that powers VS Code), Prettier, Emmet, Vim/Emacs modes, Babel, TypeScript, SCSS, Less, PostCSS, Jest and Testing Library, among others. All these tools run seamlessly in the browser without any installations or configurations. It feels like a very light-weight version of your own local development environment including the keyboard shortcuts, IntelliSense and code navigation features.
-
How to setup a simple static website using Svelte (with login)
Usually, one of the first things I do on creating a new web app is to throw a UI library in to help style components. There are several UI libraries that can be used by Svelte, but in this case I went with daisyUI because it's a fairly popular UI library which includes tailwind. To install daisyUI, you first need to install tailwind. There's a few different ways to do this (such as this guide), but the easiest way I've found is the following command, which also adds PostCSS and AutoPrefixer:
-
Vanilla+PostCSS as an Alternative to SCSS
Vanilla CSS has taken a similar path with ambitious working drafts, better browser support, and PostCSS to fill the gap for user agents lagging behind. So why is Sass/SCSS still so popular? Maybe we go so used to it that we might have forgotten what problems it was meant to solve in the first place.
What are some alternatives?
linaria - Zero-runtime CSS in JS library
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
identity-obj-proxy - An identity object using ES6 proxies. Useful for mocking webpack imports like CSS Modules.
emotion - 👩🎤 CSS-in-JS library designed for high performance style composition
vanilla-extract - Zero-runtime Stylesheets-in-TypeScript
esbuild - An extremely fast bundler for the web
twin.macro - 🦹♂️ Twin blends the magic of Tailwind with the flexibility of css-in-js (emotion, styled-components, solid-styled-components, stitches and goober) at build time.
Tailwind CSS - A utility-first CSS framework for rapid UI development.
stitches - [Not Actively Maintained] CSS-in-JS with near-zero runtime, SSR, multi-variant support, and a best-in-class developer experience.
purgecss - Remove unused CSS
tailwindcss-classnames - Functional typed classnames for TailwindCSS
JSS - JSS is an authoring tool for CSS which uses JavaScript as a host language.