critters
csso
critters | csso | |
---|---|---|
7 | 5 | |
3,374 | 3,728 | |
0.4% | 0.2% | |
6.6 | 0.0 | |
about 2 months ago | 10 months ago | |
JavaScript | JavaScript | |
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.
critters
-
Show HN: Jampack – Optimizes static websites as a post-processing step
I'm interested in the notion of identifying "critical" CSS that should be inlined rather than live in its own stylesheet.
I was hoping there was some principled way of identifying critical and non-critical CSS (e.g. user interaction effects like :hover would always be considered non-critical), but it looks like the library it's using just tries to render your page and do a best-effort detection on which rules are considered critical, which is a little unsatisfying: https://github.com/GoogleChromeLabs/critters
-
Optimize CSS with SAT Solving
https://github.com/GoogleChromeLabs/critters Might be a good starting point. It’s designed to inline the css afterward so it’s more focused on extracting used css than removing unused.
-
Critical CSS and Next.js App Directory
With the Pages dir, we had experimental support for critters. That was good enough for me
-
Remove CSS Styles and Apply Styles to All Elements
Critters does something similar but it is intended to inline only the CSS that is visible upon the page load (top of the page). There is also a Vite plugin that inlines everything that is possible to inline
-
Optimizing CSS Performance in Nuxt with Critters
// nuxt.config.js import { defineNuxtConfig } from 'nuxt' export default defineNuxtConfig({ modules: ['@nuxtjs/critters'], critters: { // Options passed directly to critters: https://github.com/GoogleChromeLabs/critters#critters-2 config: { // Default: 'media' preload: 'swap', }, }, })
-
Critical CSS? Not So Fast
I find critters[0] quite easy to work with and well worth implementing on my nextjs or Astro projects.
I build a lot of landing pages so there are very few multi page visits.
[0] https://github.com/GoogleChromeLabs/critters
-
Vue Webpack - possible to extract some CSS but not all?
Doesn't critters do this already? https://github.com/GoogleChromeLabs/critters I could be wrong though
csso
-
Optimize CSS with SAT Solving
I may have skipped a step or 2 but that was basically it. I then used satcss' output with this tool
https://css.github.io/csso/csso.html
to beautify and further organize it
-
What is a CSS minifier that works?
Not a ST plugin itself but I've used it for years: link
-
Developer daily routine job Guide
👉 Optimize your CSS with CSSO 🔗 link
-
Dark mode for French Wordle
I use an antiquity to compress CSS (Microsoft Ajax Minifier) and it didn't hold up against CSS variables :( So for now, I went to the first comer, namely CSSO, via its csso-cli version to do the job.
- Mode sombre pour Wordle en français
What are some alternatives?
compression-webpack-plugin - Prepare compressed versions of assets to serve them with Content-Encoding
csso-cli - Command line interface for CSSO
critters - CSS optimization using critters for Nuxt
rest-php
webpack-assets-manifest - This webpack plugin will generate a JSON file that matches the original filename with the hashed version.
website - My portfolio website
mangle-css-class-webpack-plugin - Minifies and obfuscates the class names in your existing JavaScript, CSS, and HTML without any modern css modules.
xhr
critical - Extract & Inline Critical-path CSS in HTML pages
scroll-to-top
penthouse - Generate critical css for your web pages
copy-text-using-javascript - copy text from field suing javascript