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

fcanvas

v1.1.6

Published

A powerful 2d canvas library that allows minimal rendering and provides diverse shapes.

Downloads

43

Readme

fcanvas

A powerful 2d canvas library that allows minimal rendering and provides diverse shapes

NPM Size Languages License Download

Documention

References: https://fcanvas.js.org


Which dist file to use?

From CDN or without a Bundler

  • index.browser(.min).global.js:

    • For direct use via <script src="..."> in the browser. Exposes the fCanvas global.
    • Note that global builds are not UMD builds. They are built as IIFEs and is only meant for direct use via <script src="...">.
    • Leaves prod/dev branches with window.__DEV__ guards (must be replaced by bundler)
    • Inlines all fCanvas core internal packages - i.e. it's a single file with no dependencies on other files. This means you must import everything from this file and this file only to ensure you are getting the same instance of code.
    • Contains hard-coded prod/dev branches, and the prod build is pre-minified. Use the *.min.global.js files for production.
  • index.browser(.min).mjs:

    • For usage via native ES modules imports (in browser via <script type="module">.
    • Shares the same runtime compilation, dependency inlining and hard-coded prod/dev behavior with the global build.

With a Bundler

  • index.mjs:

    • For use with bundlers like webpack, rollup and parcel.
    • Leaves prod/dev branches with process.env.NODE_ENV guards (must be replaced by bundler)
    • Does not ship minified builds (to be done together with the rest of the code after bundling)
    • Imports dependencies (e.g. @vue/reactivity)
      • Imported dependencies are also esm-bundler builds and will in turn import their dependencies (e.g. @vue/reactivity)
      • This means you can install/import these deps individually without ending up with different instances of these dependencies, but you must make sure they all resolve to the same version.
  • `index.js:

    • Like index.mjs but use CommonJS