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

@orditjs/core

v0.2.1-beta.5

Published

Core de libreria Ordit v2: normalizacion y contratos runtime sin framework ni discovery.

Readme

@orditjs/core

Core building blocks for Ordit-compatible runtimes.

Use this package when you want to normalize Ordit binding definitions or build a custom runtime/host that speaks the same contracts as the ordit framework. It depends on @orditjs/contracts and deliberately avoids framework discovery, Node-specific sandboxing, CLI code and vendor SDKs.

Install

npm install @orditjs/core @orditjs/contracts

What is inside

  • NormalizeBindingDefinition: validates a BindingDefinitionDraft and applies deterministic defaults.
  • RuntimeEngine: executes a normalized BindingDefinition against a RuntimeEnvelope using injected ports.
  • BindingDefinitionValidationError: deterministic validation failure for invalid binding drafts.
  • Runtime DTOs: RuntimeEngineRequest, RuntimeEngineResult, RuntimeEngineStatus.

Normalize a binding

import { NormalizeBindingDefinition } from '@orditjs/core'

const binding = new NormalizeBindingDefinition().execute({
  name: 'normalize-user',
  triggers: [
    {
      type: 'http',
      key: 'http.POST.users',
      method: 'POST',
      path: '/users',
      eventType: 'user.received',
    },
  ],
})

console.log(binding.handler.cwd)
// functions/normalize-user

Execute through ports

RuntimeEngine does not load files, spawn Node processes or publish to real brokers by itself. You inject adapters that implement the contracts from @orditjs/contracts.

import { RuntimeEngine } from '@orditjs/core'
import { createEnvelope, createEvent } from '@orditjs/contracts'

const engine = new RuntimeEngine(
  sandboxRunner,
  publisher,
  executionLedger,
  idempotencyStore,
  retryEngine
)

const result = await engine.execute({
  executionId: 'exec-1',
  binding,
  input: createEnvelope(createEvent('user.received', { userId: 'u-1' }), {
    messageId: 'msg-1',
    correlationId: 'corr-1',
    occurredAt: new Date().toISOString(),
    metadata: {},
  }),
  receivedAt: new Date().toISOString(),
})

console.log(result.status)

Adapter responsibilities

  • SandboxRunner: executes handler code and returns outputs/logs.
  • Publisher: publishes produced envelopes.
  • ExecutionLedger: stores started/completed/failed executions.
  • IdempotencyStore: rejects duplicate execution keys.
  • RetryEngine: decides whether another attempt is allowed.

Package boundary

@orditjs/core is library behavior, not the full framework. Use ordit if you want the ready-to-use package. Use @orditjs/core if you are building a custom Ordit-compatible runtime, integration or host.