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

@muhammara/native-core

v7.2.2

Published

Shared JavaScript API for MuhammaraJS native packages

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

julianhillejulianhille

Keywords

Readme

@muhammara/native-core

npm version License Documentation status

This is an internal package. Do not install it directly.

@muhammara/native-core holds the JavaScript half of the MuhammaraJS native packages: the low-level API wrapper, the Recipe API, and the TypeScript declarations. It contains no native binary and does nothing on its own. Both user-facing native packages depend on it and install it for you:

npm install @muhammara/native              # prebuilt binary
npm install @muhammara/native-with-source  # prebuilt or local source build

Its version always matches the native package that depends on it, so do not pin or upgrade it separately.

How The Packages Fit Together

MuhammaraJS is one PDF engine shipped in two ways. The same C++ library, PDF-Writer, sits at the bottom of every package; what differs is how it reaches your JavaScript.

                      PDF-Writer (C++)
                 ┌────────────┴────────────┐
      Node.js native addon         WebAssembly build
                 │                         │
     @muhammara/native-core         @muhammara/wasm
      (shared JS, internal)     (browsers, Workers, Node.js)
         ┌───────┴────────┐
@muhammara/native  @muhammara/native-with-source
  (prebuilt only)    (prebuilt or source build)

| Package | Install it when | | ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | | @muhammara/native | You run Node.js on a platform with a prebuilt binary. This is the default choice. | | @muhammara/native-with-source | No prebuilt matches your platform, or Electron must rebuild the addon. | | @muhammara/wasm | You work in a browser or Web Worker, or cannot load native addons (for example some serverless runtimes). | | @muhammara/native-core | Never directly. Both native packages depend on it and install it for you. |

Both native packages expose the identical API, so switching between them is a dependency change, not a code change. The Wasm package produces the same PDFs, but it is byte-first (Uint8Array, ArrayBuffer, Blob, File) instead of path-, stream-, and Buffer-oriented, so its JavaScript API is separate.

Links