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

purify-amp-css

v1.1.1

Published

A Jest matcher to validate AMP markup

Downloads

5

Readme

Purify AMP CSS

npm version

AMP pages currently have a 75KB CSS limit.

This package aims to help you stay within that limit by monkey patching the Node HTTP ServerResponse so that when markup is returned from the server the contents of the <style amp-custom> element can be run through PurifyCSS, removing any unused styles and replacing with a purified and minified version.

As AMP pages are served from the AMP cache any performance hit taken when initially rendering the page shouldn't matter in production.

Installation

yarn add purify-amp-css -D

Usage

Here's an example using Express:

import express from 'express';
import purifyAmpCss from 'purify-amp-css';

const app = express()

app.use(purifyAmpCss.middleware());

Here's an example using Node's HTTP server:

import http from 'http';
import { purifyAmpCss } from 'purify-amp-css';
import myAmpMarkup from './some/markup';

http.createServer((req, res) => {
  purifyAmpCss(req, res);

  res.end(myAmpMarkup);
}).listen(8080);

Here's an example using Next.js:

import Document, { Html, Head, Main, NextScript } from 'next/document';
import { purifyAmpCss } from 'purify-amp-css';

class MyDocument extends Document {
  static async getInitialProps(ctx) {
    const initialProps = await Document.getInitialProps(ctx);

    purifyAmpCss(ctx.req, ctx.res);

    return { ...initialProps };
  }

  render() {
    return (
      <Html>
        <Head />
        <body>
          <Main />
          <NextScript />
        </body>
      </Html>
    )
  }
}

export default MyDocument;

Configuration

An options object can be passed to the named export like so:

import { purifyAmpCss } from 'purify-amp-css';

const options = { minify: true };

purifyAmpCss(req, res, options);

Or when using the Express middleware:

import purifyAmpCss from 'purify-amp-css';

const options = { minify: true };

app.use(purifyAmpCss.middleware(options));

The following options are available:

| Option | Description | Default | |-------------|----------------------------------------|---------| | minify | Minify the AMP CSS | true | | whitelist | Array of selectors to always leave in | [] | | debug | Log the amount of CSS that was removed | false |