webpack-config-plugins
critters
| webpack-config-plugins | critters | |
|---|---|---|
| 1 | 7 | |
| 639 | 3,374 | |
| 0.0% | 0.4% | |
| 0.0 | 6.6 | |
| 11 months ago | about 2 months ago | |
| JavaScript | JavaScript | |
| MIT License | Apache License 2.0 |
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.
webpack-config-plugins
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
What are some alternatives?
prerender-spa-plugin - Prerenders static HTML in a single-page application.
compression-webpack-plugin - Prepare compressed versions of assets to serve them with Content-Encoding
vscode-file-nesting-config - Config of File Nesting for VS Code
critters - CSS optimization using critters for Nuxt
workerize-loader - 🏗️ Automatically move a module into a Web Worker (Webpack loader)
webpack-assets-manifest - This webpack plugin will generate a JSON file that matches the original filename with the hashed version.
copy-webpack-plugin - Copy files and directories with webpack
mangle-css-class-webpack-plugin - Minifies and obfuscates the class names in your existing JavaScript, CSS, and HTML without any modern css modules.
offline-plugin - Offline plugin (ServiceWorker, AppCache) for webpack (https://webpack.js.org/)
critical - Extract & Inline Critical-path CSS in HTML pages
penthouse - Generate critical css for your web pages
svg-spritemap-webpack-plugin - SVG spritemap plugin for webpack