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

@injoffice/native-runtime

v0.1.1

Published

Browser-safe worker protocol and lifecycle for InjOffice native WASM engines.

Readme

@injoffice/native-runtime

Browser-safe worker protocol and lifecycle shared by the optional InjOffice WASM format packages. This package contains no Office parser and no WASM binary. Install a format package such as @injoffice/xlsx-wasm to process files.

The runtime deliberately requires an injected worker factory. Importing it is safe in Node.js and server-rendered applications, and format packages remain responsible for resolving their own worker and WASM assets.

import { createNativeWasmClient } from '@injoffice/native-runtime'

const client = createNativeWasmClient({
  format: 'xlsx',
  workerFactory: () => new Worker(workerUrl),
  assets: { wasmUrl, goRuntimeUrl },
})

const contractJson = await client.extract(fileBytes)
const savedBytes = await client.apply(fileBytes, mutationJson, expectedRevision)
client.terminate()

Calls are serialized because each worker owns one native engine instance. Input buffers are snapshotted when an operation is called and the snapshots are transferred later, so queued work cannot observe caller mutations and the caller's authoritative bytes are never detached. A timeout, abort, fatal worker error, or malformed matching response terminates the worker; the next call starts a fresh instance. Workers may also send the versioned unsolicited fatal notification when an already-ready native engine exits, so the runtime discards it while idle rather than posting the next operation to a dead worker.