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

@hfour/imager-wasm

v0.0.1

Published

selected image-rs function into wasm for nodejs

Downloads

5

Readme

imager-wasm

Build Status

This a simple package to compile selected functions from the image-rs rust package to wasm, and make them available to nodejs. It's configured to support at least GIF, PNG and JPEG (but this may vary depending on our needs).

We don't wrap the whole of image-rs because the .wasm file will be too big, and then there's no nodejs build system that could only take parts of that .wasm file. The rust linker though will only include the used functions in the .wasm file.

Setup

rustup target add wasm32-unknown-unknown
cargo install wasm-pack
~/.cargo/bin/wasm-pack build --release -t nodejs

Example usage from node (sync code):

fs = require('fs');
img1 = fs.readFileSync('problem.jpg');

m = require('./pkg/imager_wasm');
img2 = m.thumbnail(img1, 800, 800);

fs.writeFileSync('solution.jpg', img2);

References

  • https://rustwasm.github.io/docs/wasm-pack/
  • https://rustwasm.github.io/docs/wasm-bindgen/
  • https://www.joyent.com/blog/improved-wasm-support-coming-to-node
  • https://dev.to/dandyvica/wasm-in-rust-without-nodejs-2e0c

Making a release on npmjs

This repo has travis configured to publish the build node package on npmjs. When a commit on the master branch is tagged, travis will try to push the package to npmjs. The version of the node package is copied from Cargo.toml, so it's up to you make sure the version is updated accordingly. The tag name is not used, but should follow the version in Cargo.toml (and so the node package version). For example, the 0.1.0 version should be tagged as v0.1.0.