npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@plone/critical-css-cli

v1.0.2

Published

A CLI to generate critical css from any url

Downloads

23

Readme

@plone/critical-css-cli

A command-line utility to generate critical CSS from a set of URLs. The functionality is useful for a CMS-powered website, where pages are user-defined and and their CSS comes from multiple addons. Because the website layout is generated based on the CMS content, it would be impossible to understand what is Critical CSS at build time, only once the website is moved to production and the "dust settles" on the main pages structure.

Typically, for the best possible performance, you'd want to generate the critical CSS as short as possible and that means one CSS per separate page. But this complicates things: async runners, file refresh, file invalidations, etc, would have to be taken into account. This raises the barrier of entry for the project.

This package tries to keep things really simple by accepting some limitations. A single CSS file is generated based on multiple provided URLs. The CSS is optimized automatically using postcss and cssnano, so duplicated rules are eliminated.

Install globally

npm install -g @plone/critical-css-cli

Then you can use it like:

critical-cli -h

Install from this repo

Either install it as a native package with: yarn install or npm install.

Then run the generator like:

bin/critical-cli -o ./out/critical.css https://plone.org

This will generate a file called critical.css in the out folder.

Run bin/critical-generator -h to see full options.

Use via docker

Alternatively, you can use docker to build and use this package. Pass website url for which critical css has to be generated as env var to docker-compose

URL=<website-url> docker-compose up

Config

Pass the DIMENSIONS env variable if you want to deliver critical CSS for multiple screen resolutions. Defaults to 1300x900 if you don't want.

URL=<website-url> DIMENSIONS="1220x300,1345x500" docker-compose up

Location to save the critical.css file. Defaults to /var/app/output/critical.css (inside the docker container)

URL=<website-url> LOCATION="output/<your-dir>/critical.css" docker-compose up

The location is relative to the current directory.