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

acsync-core

v1.0.1

Published

Incremental update/patch system for binary files. .NET Core library exposed via node-api-dotnet.

Readme

acsync-core

Incremental update/patch system for binary files. .NET Core library exposed for Node.js via node-api-dotnet.

Install

npm install acsync-core

Requires Node.js 18+ and the .NET 10 runtime (bundled with node-api-dotnet).

Usage

const acsync = require('acsync-core');

// 1. Scan a directory to create a manifest
const manifest = acsync.createManifest('D:\\app\\v2.0');
console.log(`Found ${manifest.files.length} files`);

// 2. Save/Load manifest
acsync.saveManifest(manifest, './manifest.json');
const loaded = acsync.loadManifest('./manifest.json');

// 3. Diff two manifests
const oldManifest = acsync.loadManifestFromDirectory('D:\\app\\v1.0');
const newManifest = acsync.createManifest('D:\\app\\v2.0');
const { changed, deleted } = acsync.diff(oldManifest, newManifest);
console.log(`${changed.length} changed, ${deleted.length} deleted`);

// 4. Create a patch
acsync.createPatch('D:\\app\\v1.0', 'D:\\app\\v2.0');

// 5. Apply a patch (requires 7za.exe in PATH or app directory)
acsync.applyPatch('D:\\app\\user', null, ['.json', '.yaml']);

API

| Method | Description | |---|---| | createManifest(path) | Scan directory, return manifest with SHA256 hashes | | saveManifest(manifest, filePath) | Save manifest to JSON file | | loadManifest(filePath) | Load manifest from JSON file | | loadManifestFromDirectory(path) | Load manifest from a directory's acsync_manifest.json | | diff(oldManifest, newManifest) | Compare two manifests, return { changed, deleted } | | createPatch(oldPath, newPath, outputPath?) | Build delta patch as .7z | | applyPatch(targetPath, patchFile?, excludeExts?) | Apply patch to target directory |

Note: createPatch and applyPatch require 7za.exe (from 7-Zip.CommandLine) to be available in the process working directory or PATH.

Requirements

  • Node.js >= 18
  • .NET 10 runtime (auto-installed by node-api-dotnet)
  • Windows (for patching with 7za.exe; manifest scanning works cross-platform)