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

@codemation/core-nodes-ocr

v0.2.6

Published

Azure AI Content Understanding (OCR) plugin for Codemation — prebuilt document, invoice, and image analyzers.

Readme

@codemation/core-nodes-ocr

Azure AI Content Understanding OCR integration for Codemation. Exposes three prebuilt analyzer nodes for document, invoice, and image analysis — designed to make it trivial to wire up OCR-powered workflows.

Install

pnpm add @codemation/core-nodes-ocr

Nodes

  • analyzeInvoiceNode — runs the prebuilt-invoice analyzer; returns markdown + structured fields. The prebuilt-invoice ID is verified against the Azure SDK.
  • analyzeDocumentNode — runs the prebuilt-document analyzer by default; accepts a custom analyzerId. The default ID follows Azure's published naming conventions but is not verified against a live resource — pass your own analyzerId if Azure returns "analyzer not found."
  • analyzeImageNode — runs the prebuilt-imageAnalyzer by default; accepts a custom analyzerId. Same caveat as analyzeDocumentNode.

All three nodes read their input from item.binary (default key: "data") and emit { content: string; fields: Record<string, unknown> } as the item payload. Binary bytes are never put in item.json.

Credential

Register an azureContentUnderstandingCredentialType credential with:

  • Endpoint (public) — your Azure resource endpoint, e.g. https://your-resource.cognitiveservices.azure.com/
  • API key (secret)

Usage

import { analyzeInvoiceNode, azureContentUnderstandingCredentialType } from "@codemation/core-nodes-ocr";

// Wire up in your workflow:
workflow
  // assume a binary PDF is attached as item.binary["data"]
  .then(analyzeInvoiceNode.create({ binaryField: "data" }, "Extract invoice fields"));

The output item's json will contain:

{
  content: "# Invoice\n\n...",   // markdown text from the analyzer
  fields: {                      // structured fields (dates, amounts, line items, etc.)
    VendorName: "Acme Corp",
    InvoiceTotal: 1234.56,
    // ...
  }
}

For custom analyzer IDs (e.g. a fine-tuned model), pass analyzerId:

analyzeDocumentNode.create({ analyzerId: "my-custom-model", binaryField: "doc" }, "Analyze contract");

Output shape

All three nodes return the same OcrAnalysisOutput type:

type OcrAnalysisOutput = {
  content: string; // markdown representation of the document
  fields: Record<string, unknown>; // structured fields from the prebuilt model
};

Multi-page results are merged into a single content string; the fields property reflects the primary or first content segment unless the analyzer returns multiple segments (in which case a segments array is included).