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

@vitalyros/opencvjs-wasm-separate

v4.5.2

Published

Build of opencv.js with separate js and wasm files

Downloads

1

Readme

Opencv JS separate wasm build

Build of opencv.js with separate js and wasm files

Version of this npm package corresponds with opencv version

How to use?

  • install with npm npm install @vitalyros/opencvjs-separate-wasm
  • make node_modules/@vitalyros/opencvjs-separate-wasm/opecvjs.wasm file accessible for fetch requests. This depends on where you want to store this wasm file. If you don't need to store it separately from js file, then why are you using this? Use the common package.
  • In your javascript
    • import default from javascript part of the package import {default as initOpencvJs} from "@vitalyros/opencvjs-separate-wasm"; FYI this is a factory function see MODULARIZE=1 in emscripten docs
    • fetch wasm let wasm = await fetch("http://mysite/opencvjs.wasm");
    • turn wasm into a buffer let buffer = await wasm.arrayBuffer();
    • initialize opencv.js cv = await initOpencvJs({wasmBinary: buffer});
    • use cv as described in opencv.js docs

e.g. for wasm stored as separate file in web extension

import {default as initOpencvJs} from "@vitalyros/opencvjs-separate-wasm";

var cv;

(async() => {
    let url = browser.extension.getURL("./dist/ext/opencv/opencv.wasm");
    let wasm = await fetch(url);
    let buffer = await wasm.arrayBuffer();
    cv = await initOpencvJs({
        wasmBinary: buffer
    });
    // cv.imread(image)
})();