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

@abapify/adt-flow

v0.4.10

Published

Incremental transport source-tree materialization for ADT

Readme

@abapify/adt-flow

Incremental transport source-tree materialization for ADT. The service checks out either the exact source boundary immediately before a transport scope or the newest exact source in that scope.

Register the command and configure the active format in adt.config.ts:

import { defineConfig } from '@abapify/adt-config';

export default defineConfig({
  commands: ['@abapify/adt-flow/commands/flow'],
  flow: {
    format: { id: 'abapgit', options: { folderLogic: 'prefix' } },
    include: { objectTypes: ['CLAS', 'INTF'] },
    concurrency: { metadata: 4, sources: 4 },
  },
});

Then reconcile the current directory to either side of the transport boundary:

adt flow checkout tr DEVK900001 --base
adt flow checkout tr DEVK900001
adt flow checkout tr DEVK900001,DEVK900002 --base
import {
  createAdtFlowService,
  createAdtFlowDependencies,
} from '@abapify/adt-flow';
import { getFormatPlugin } from '@abapify/adt-plugin';

// Use the format plugin already registered by @abapify/adt-plugin-abapgit
const registeredFormatPlugin = getFormatPlugin('abapgit');
if (!registeredFormatPlugin) {
  throw new Error('abapGit format plugin is not registered.');
}

const flow = createAdtFlowService(
  createAdtFlowDependencies(client, registeredFormatPlugin),
);

await flow.checkout({
  root: process.cwd(),
  transports: ['DEVK900001'],
  mode: 'base',
  config: {
    format: { id: 'abapgit', options: { folderLogic: 'prefix' } },
    include: { objectTypes: ['CLAS', 'INTF'] },
  },
});

The service invokes no Git command. It reconciles format-owned files and deterministic descriptors under .adt, rejects unowned collisions or modified indexed files before mutation, and rolls back a failed multi-file apply. Branches, commits, routing, and merge requests remain the caller's concern.

.adt/tr/<transport>.json is emitted for every request/task discovered during head checkout. Each transport descriptor retains the complete CTS object inventory, including unsupported or currently filtered types. Object descriptors under .adt/objects/ are written for both base and head. Object descriptors use .adt/objects/<TYPE>/<unique-name>.<type>.adt.json. The index stores hashes and immutable version identities, never source bodies or credentials. In an explicit partial checkout, an object that cannot be materialized still receives an omitted descriptor with its identity and component diagnostic, but no owned files or source selection. Removing .adt only removes the optimization; source selection continues to come from the supplied SAP manifest operation.

Exactness applies to versioned source components. Metadata files describe the object metadata available at checkout time; flow does not reconstruct historical metadata or replicate repository history.