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

@marketing-relevance/postcss-font-awesome

v1.0.3

Published

PostCSS plugin to pull in a Font Awesome's icon unicode

Downloads

2

Readme

PostCSS Font Awesome Build Status

PostCSS plugin to pull in a Font Awesome's icon unicode using content.

Before

.foo::before {
  font-awesome: camera;
}

After

.foo::before {
  content: '\f030';
}

The font-family and font-weight attributes will need to be supplied manually in your CSS, as the plugin will not provide those values. This ensures the plugin can be as flexible as possible, and is better handled using something like CSS custom variables just in case Font Awesome changes these values in the future.

Example

:root {
    --fa-light: 300;
    --fa-brand: 400;
    --fa-regular: 400;
    --fa-solid: 900;
    --fa-duotone: 900;

    --fa-font-family: 'Font Awesome 5 Free';
    --fa-font-family-brands: 'Font Awesome 5 Brands';
    --fa-font-family-duotone: 'Font Awesome 5 Duotone';
}

.icon::before {
    font-family: var(--fa-font-family);
    font-weight: var(--fa-solid);
    font-awesome: camera;
}

Options

Font Awesome Pro

By default the plugin will use the free version of Font Awesome. If you are using the pro version of Font Awesome, simply set the option:

require('@marketing-relevance/postcss-font-awesome')({
    fontAwesomePro: true, // defaults to false
})

Usage

postcss([ require('@marketing-relevance/postcss-font-awesome')({
    fontAwesomePro: false, // defaults to false
}) ])

Font Awesome must be installed using a package manager in order for this plugin to work: https://fontawesome.com/how-to-use/on-the-web/setup/using-package-managers

See PostCSS docs for examples for your environment.

TODO

  • [ ] Maybe add an option to use the font awesome API and supply an api key to fetch pro icons so the NPM package doesn't need to be installed. Useful when using font awesome's kit's or CDN.