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

svg-patcher

v0.3.0

Published

Save bandwidth by patching SVG files instead of downloading them multiple times

Downloads

8

Readme

svg-patcher

When you are using several similar SVG files in the same project, you should edit them using JavaScript instead of downloading many slightly different versions of the same image. This library attempts to make this easy.

Try the example

Just start example/example.html in your browser.

If you use Chrome you need to start it with the flag --allow-file-access-from-files. Don't worry, your users won't have to do that. This is only needed when loading files from the file system.

How to use

Simply include svg-patcher.js in your project. It will export svgPatcher in the global scope.

svgPatcher.fetch(url)

  • url: String

This function returns a Promise that resolves with a SVG Document.

svgPatcher.fetch('https://getkey.eu/magnifying_glass_icon.svg').then(svgDocument => {
	console.log(svgDocument);
});

svgPatcher.patch(svgDocument, patcher[, clonable])

  • svgDocument: Document
  • patcher: Function
  • clonable: Boolean

patcher takes the SVG Document you pass to svgPatcher.patch() as an argument.

svgPatcher.patch() returns a Promise that resolves with a patched Image.

function patcher(svgDocument) {
	// navigate and modify the SVG's DOM however you want
	svgDocument.children[0].setAttribute('fill', 'yellow');
}

svgPatcher.patch(svgDocument, patcher).then(img => {
	document.body.appendChild(img);
});

If clonable is unset or set to false, the resolved image will not be clonable, ie:

let newImg = oldImg.cloneNode(true); // won't work

let newImg = new Image(); // won't
newImg.src = oldImg.src; // work

If you set clonable to true, once you are done cloning it, you should release memory by calling svgPatcher.revoke().

svgPatcher.revoke(img)

  • img: Image

Releases the memory used to load your Image. Use this function only if you no longer need to clone your image.

It is only useful to use this function on clonable images.

You can use this function on the original Image or any of its clones.