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

@gemini-testing/canvas-prebuilt

v1.6.16

Published

Prebuilt versions of node-canvas as a drop-in replacement

Downloads

17

Readme

NPM version

NOTE

This fork is only for install script fix in 1.6.x version: https://github.com/node-gfx/node-canvas-prebuilt/pull/13

This is a drop-in replacement for canvas that does not require any compiling. To use it just npm install canvas-prebuilt or replace canvas with canvas-prebuilt in your dependencies.

You will also need to change require('canvas') to require('canvas-prebuilt').

The repo is just a set of scripts that downloads a specific node-canvas version, builds it and bundles it on all platforms. It's meant to run on Travis and AppVeyor but it can be run locally too

Linux technicalities

Linux users will need glibc >= 2.13.1 (Ubuntu 14.04+, Debian 7+, etc)

If you are using fonts, you might see some FontConfig warnings which are harmless:

| Situation | Message | Meaning | | --------- | ------- | ------- | | You have an old version of FontConfig on your system | Fontconfig warning: line 142: blank doesn't take any effect anymore. please remove it from your fonts.conf | You don't need to do anything, but removing said line or upgrading FontConfig on your system should fix it | | You don't have FontConfig | Fontconfig error: Cannot load default config file | You don't have any fonts on your system, so if you want to use the text APIs you'll either need to install FontConfig or use Canvas.registerFont |

Releases

More detail on the releases below, this won't be relevant to most users.

Binaries

Make sure your node version is the most recent to guarantee ABI compatibility

| [email protected][email protected][email protected][email protected][email protected][email protected] | node 8 | node 7 | node 6 | node 5 | node 4 | node 0.12 | node 0.10 | | ------------------ | ------ | ------ | ------ | ------ | ------ | --------- | --------- | | Linux x64 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | Windows x64 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | OSX x64 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | Windows x86 | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | | Linux x86 | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | | Linux ARM | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ |

| [email protected][email protected][email protected] | node 9 | node 8 | node 7 | node 6 | node 5 | node 4 | | ------------------ | ------ | ------ | ------ | ------ | ------ | ------ | | Linux x64 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | Windows x64 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | OSX x64 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | Windows x86 | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | | Linux x86 | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | | Linux ARM | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ | 𐄂¹ |

¹I have some ideas on how to get these working with cross-compilation if people request it. I plan to add Linux/ARM

Bundling

The bundling scripts just take a regularly compiled executable (canvas.node in this case) and look at which non-system libraries it links against. Those libraries are then copied to the release directory and binaries are updated if necessary to refer to them.

The strategies for bundling could be applied to other projects too since they're general:

  • On macOS, macpack is used to search dependencies, filter out non-system ones, and update binary references
  • On Windows, Dependency Walker's CLI is used to search dependencies. Anything in the MSYS2 folder is considered non-system. Patching is not necessary because Windows looks for dlls in the same folder as the binary
  • On Linux, pax-utils searches dependencies, and everything not in /lib is non-system. The custom binding.gyp compiles canvas.node to look inside its own directory for dependencies