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

sass-inline-svg-utf8

v1.0.5

Published

Inline SVGs in your CSS as html-encoded UTF-8, string replacement included.

Downloads

40

Readme

#sass-inline-svg-utf8

Build Status npmjs

Inline SVGs in your CSS as html-encoded UTF-8 with node-sass.

Inlining is good because fewer requests, html-encoded is good for SVG because it is smaller than base64 (by about 30% on average).

String replacement is good because you can use 'variables' in your SVG source files and replace them on a per-inlined-instance basis. Use case? You need a white, a black, and a blue arrow icon, and can create them on the fly when inling from a single source file. Good because if the arrow needs to be changed, you only have to change on file, not three.

Install

npm install --save-dev sass-inline-svg-utf8

Usage

var sass = require('node-sass');
var sassInlineSVG = require('sass-inline-svg-utf8');

sass.render({
  functions: sassInlineSVG(),
  file: file,
  outfile: outfile
}, function(error, result) {
    /* Your code here */
});

In your Sass:

.myClass {
  background-image: inline-svg('./images/logo.svg');
}

For optimal results and minimal filesize, run your SVGs through SVGO first (Actually, I'm on the fence whether to include SVGO optimization by default when inlining, but I’m not sure because of various settings/complexity). If you have a strong opinion on that, let’s dicuss here.

Advanced Usage w/ String replacement

In your SVG source, you can use variable strings to replace when inlining:

<path fill="fillcolor" […] />

In your Sass, you can pass a map of variables to replace as a second parameter:

.myClass {
  background-image: inline-svg('./images/arrow.svg', { fillcolor: '#000000'});
}

This will replace all occurences of fillcolor in the SVG file with #000000 in the inlined SVG.

If you want to use $-prepended variable names to match your Sass variables, quote them in the Sass map like { '$fillcolor': '#000000' }.

This will result in (not html encoded here for readability):

<path fill="#000000" […] />

So to create three instances of the same SVG source with different fill colors in your CSS:

.red-arrow {
  background-image: inline-svg( './images/arrow.svg', ( fillcolor: 'red'));
}

.blue-arrow {
  background-image: inline-svg( './images/arrow.svg', ( fillcolor: 'blue'));
}

.black-arrow {
  background-image: inline-svg( './images/arrow.svg', ( fillcolor: 'black'));
}

Using colors

To use non-named colors like hex, rgba etc., these need to be passed as a quoted string (this is down to the current behavior of node-sass/libsass):

.white-arrow {
  background-image: inline-svg( './images/arrow.svg', ( fillcolor: '#fff'));
}

Whn using variables that may contain colors, these need to be evaluated to be on the safe side:

.custom-arrow {
  background-image: inline-svg( './images/arrow.svg', ( fillcolor: #{$custom-color}));
}

I have opened this issue with node-sass to make the quoting/evaluating unnecessary (fingers crossed…)