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

@emdzej/ncsx-wire

v0.5.1

Published

Shared EdiabasLike type contract — minimal Ediabas-shape that ncsx packages consume without hard-depending on @emdzej/ediabasx-ediabas.

Readme

@emdzej/ncsx-wire

Shared type contracts for talking to EDIABAS — re-exported by every ncsx package that needs a minimal Ediabas-shape without pulling in @emdzej/ediabasx-ediabas directly.

export interface EdiabasLike {
  loadSgbd(filename: string): Promise<void>;
  executeJob(
    jobName: string,
    options?: { params?: string[]; timeout?: number },
  ): Promise<EdiabasJobResultLike[][]>;
  isConnected(): boolean;
}

export interface EdiabasJobResultLike {
  name: string;
  type: string;
  value: unknown;
}

History

The package used to host wire-direct helpers (readCoding, applyCodingPlan, readCodingIndex, identify) that ran each EDIABAS job through apiJob directly, bypassing the per-CABD A_*.ipo dispatcher. Those covered the early bring-up but silently skipped the IPO's auth gates, multi-step write protocols, and checksum recalculation steps — see docs/ipo-usage.md for why that matters.

Both flows now route through the IPO instead:

  • ReadprocessReadCoding in apps/web/src/lib/process-ecu.tscabimain("CODIERDATEN_LESEN").
  • WriteprocessWriteCoding in the same file → cabimain("SG_CODIEREN").

Both use @emdzej/ncsx-inpax-cabi-provider's real BinBuf + slot-table machinery so the SGBD's C_S_LESEN / C_S_SCHREIBEN calls see the request packet NCSEXPER would have built. The wire-direct helpers were removed once the IPO path covered the same surface; only the shared types stayed.

Consumers

  • @emdzej/ncsx-identityEdiabasLike parameter for FA / ZCS / VIN readers.
  • @emdzej/ncsx-inpax-cabi-providerEdiabasLike in CdhContext.ediabas.