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

@fpipita/babel-plugin-css-tag-postcss

v3.0.1

Published

Process your css tagged templates with PostCSS.

Downloads

26

Readme

babel-plugin-css-tag-postcss Travis build

If you build production apps and make use of the css tag function to style your LitElement-like webcomponents, this simple Babel plugin will come very handy as it will let you transform your css tagged templates by doing things like adding vendor prefixes, minification and all of the other stuff that can be achieved through PostCSS plugins.

For example, given the following:

// input.js
import { LitElement, css, html } from "lit-element";

const sm_min = 600;

export class MyFoo extends LitElement {
  static get styles() {
    return css`
      @media (min-width: ${sm_min}px) {
        ::placeholder {
          color: red;
        }
      }
    `;
  }

  render() {
    return html`<input type="text" placeholder="Write something" />`;
  }
}

and assuming your .postcssrc.json (or any of the other config formats supported by the postcss-load-config package) contains:

{
  "plugins": {
    "autoprefixer": {
      "overrideBrowserslist": ["edge 17, firefox 19, chrome 56"]
    }
  }
}

the plugin will output:

// output.js
import { LitElement, css, html } from "lit-element";

const sm_min = 600;

export class MyFoo extends LitElement {
  static get styles() {
    return css`
      @media (min-width: ${sm_min}px) {
        ::-webkit-input-placeholder {
          color: gray;
        }
        ::-moz-placeholder {
          color: gray;
        }
        ::-ms-input-placeholder {
          color: gray;
        }
        ::placeholder {
          color: gray;
        }
      }
    `;
  }

  render() {
    return html`<input type="text" placeholder="Write something" />`;
  }
}

Installation

$ npm install --save-dev @fpipita/babel-plugin-css-tag-postcss

You also need to have @babel/core and postcss packages installed and properly configured for your build process.

Usage

In your babel configuration, simply add:

{
  "plugins": [
    [
      "@fpipita/babel-plugin-css-tag-postcss",
      {
        "tag": "css"
      }
    ]
  ]
}

You can optionally specify the tag option, which is basically the name of the css tag function you use to define the css tagged templates in your code. It defaults to css so in most cases you can just forget about it.

The plugin will read and reuse your existing PostCSS configuration which can be expressed in any of the formats supported by the postcss-load-config package.

Template literals with embedded expressions

Despite it is best to avoid embedded expressions and make use of css custom variables to make styles that can be configured at runtime (read here why), there are cases where you can't use css custom variables just because the css cascading model doesn't apply, like within the media query list part of a @media CSS at-rule.

When the plugin encounters an embedded expression, it keeps it in place:

// input.js
css`
  @media (min-width: ${sm_min}px) {
    ::placeholder {
      color: gray;
    }
  }
`;

// output.js
css`
  @media (min-width: ${sm_min}px) {
    ::-webkit-input-placeholder {
      color: gray;
    }
    ::-moz-placeholder {
      color: gray;
    }
    ::-ms-input-placeholder {
      color: gray;
    }
    ::placeholder {
      color: gray;
    }
  }
`;

The next example is only shown with the purpose of explaining how the plugin behaves when an expression is encountered within a css rule which is expanded by PostCSS:

// input.js
css`
  @media (min-width: 600px) {
    ::placeholder {
      // don't do this, use css custom variables e.g. color: var(--my-foo-placeholder-color)
      color: ${gray};
    }
  }
`;

// output.js
css`
  @media (min-width: 600px) {
    ::-webkit-input-placeholder {
      color: ${gray};
    }
    ::-moz-placeholder {
      color: ${gray};
    }
    ::-ms-input-placeholder {
      color: ${gray};
    }
    ::placeholder {
      color: ${gray};
    }
  }
`;

Known limitations

Due to the sync nature of Babel plugins, only sync PostCSS plugins are supported.