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

@incremental/engine

v0.1.3

Published

Prebuilt native binaries for the Incremental compute engine

Readme

@incremental/engine

Prebuilt native binaries for the Incremental compute engine (core/dist/incremental).

Purpose

This package bundles the platform-specific native engine binary so consumers of @incremental/client can run incremental serve / incremental affected / incremental init etc. without building Goose from source.

Installation

npm install @incremental/engine

Binary resolution

@incremental/client resolves the engine binary through @incremental/engine.enginePath():

  1. INCREMENTAL_ENGINE environment variable (explicit override)
  2. Prebuilt binary bundled in this package (prebuilds/<platform>-<arch>/incremental)
  3. Dev-mode fallback: core/dist/incremental in the incremental monorepo

Supported platforms

| Platform | Arch | Status | | -------- | ----- | ------------------------------ | | darwin | arm64 | ✅ Prebuilt binary included | | darwin | x64 | ✅ Prebuilt binary included | | linux | x64 | Available via GitHub Releases* | | linux | arm64 | Available via GitHub Releases* |

* install.js downloads the incremental-<platform>-<arch> asset from the latest GitHub Release at install time when no prebuild is bundled; you can also build locally with make build and point INCREMENTAL_ENGINE at the result.

Building the binary

From the incremental monorepo root:

make build   # builds core/dist/incremental via Goose toolchain

Package contents

  • bin/incremental.js — CLI entry point that execs the native binary
  • index.js / index.d.ts — enginePath() and engineDir() exports
  • install.js — postinstall script (verifies prebuilt binary or downloads)
  • prebuilds/<platform>-<arch>/incremental — native engine binary

Usage

import { enginePath } from "@incremental/engine";

console.log(enginePath()); // /path/to/incremental binary

License

Apache-2.0