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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@taulabs/replicad-opencascadejs

v0.23.0-beta.0

Published

OpencascadeJS custom build for replicad (Tau fork: SIMD without relaxed-simd, native WebAssembly exceptions)

Downloads

163

Readme

replicad-opencascadejs

An opencascadejs build containing only the APIs necessary to run replicad.

Usage

import oc from "replicad-opencascadejs";

The root is a ready-to-use instance. Consumers that own initialization timing or need a fixed build should import an initializer explicitly:

import { createInstance } from "replicad-opencascadejs/single/init";
import wasmUrl from "replicad-opencascadejs/single/wasm?url";

const oc = await createInstance({ locateFile: () => wasmUrl });

Use ./init for lazy automatic selection, ./single/init or ./multi/init for a fixed variant, and the matching ./single/wasm or ./multi/wasm URL. The ./single and ./multi subpaths expose raw Emscripten factories.

Building

The build is driven by @libcascade/toolchain from the typed libcascade.config.ts in this directory. Docker must be installed on the host and its daemon must be running before any libcascade build command. The toolchain pins the image by digest, so no tags need manual syncing.

pnpm build          # both variants, then assemble the packaging surface
pnpm buildSingle    # libcascade build --variant single
pnpm buildMulti     # libcascade build --variant multi
pnpm assemble       # regenerate dist/{types,init,index,variant}.d.ts + entries

To iterate against a locally built image instead of the pinned digest, set LIBCASCADE_IMAGE (the CLI prints a provenance warning when it is active):

LIBCASCADE_IMAGE=ocjs-local:single-threaded pnpm buildSingle
LIBCASCADE_IMAGE=ocjs-local:multi-threaded pnpm buildMulti

Custom C++ bindings live in build-config/wrappers/ and are declared, with the symbols each file provides, in libcascade.config.ts.