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

@1c-odata/cli

v0.6.0

Published

CLI for @1c-odata/client: fetch 1С EDMX metadata and generate TypeScript types.

Downloads

773

Readme

@1c-odata/cli

Two binaries for @1c-odata/client:

  • 1c-odata fetch — downloads $metadata (EDMX) from a 1С:Enterprise OData V3 endpoint and saves it locally.
  • 1c-odata generate — generates TypeScript types from the saved EDMX (per-target output under generated/<target>/).

Codegen library is also exposed at @1c-odata/cli/codegen for programmatic use.

Pure ESM. Node ≥ 22.21.0.

⚠️ v0.x — pre-release. API is unstable; see STABILITY.md.

Install

pnpm add -D @1c-odata/cli @1c-odata/client

Quick start

1c-odata.config.ts:

import { parseConnectionUrl } from '@1c-odata/client'
import { defineCodegenConfig } from '@1c-odata/cli'

const url = process.env.ONEC_URL
if (!url) throw new Error('Set ONEC_URL (format: http://user:pwd@host/path)')

export default defineCodegenConfig({
  targets: {
    trade: {
      connection: {
        ...parseConnectionUrl(url),
        serverTimezone: 'Europe/Moscow',
      },
      include: ['Catalog_*', 'Document_*'],
    },
  },
})

Fetch + generate:

export ONEC_URL=http://u:[email protected]/odata/standard.odata
pnpm 1c-odata fetch
pnpm 1c-odata generate

loadConfig auto-sources .env then .env.local (relative to cwd) before evaluating 1c-odata.config.ts, so process.env.ONEC_URL resolves at config-eval time without a manual export.

Commands & flags

Both commands default to all targets; pass -t to pick one.

| Command | Flags | |---|---| | 1c-odata fetch | -t, --target <name>, --config <path> | | 1c-odata generate | -t, --target <name>, --config <path>, -f, --force (regenerate even when inputs are unchanged), --metadata-only (emit only __metadata.json; skips TS generation — existing .ts files are left untouched) |

Config options

defineCodegenConfig accepts, alongside targets:

| Option | Default | Purpose | |---|---|---| | metadataDir | ./metadata | where <target>.xml snapshots are written / read | | generatedDir | ./generated | where generated TS lands (<target>/<kind>/<Name>.ts) | | fetchTimeout | 120_000 | 1c-odata fetch timeout in ms (per-target override available) |

Each target is { connection, include?, fetchTimeout? }include is a glob whitelist of entity-type names (Catalog_*), and the dependency closure auto-expands.

Programmatic use

runFetch / runGenerate / loadConfig are exported from @1c-odata/cli (and generate from @1c-odata/cli/codegen) for scripting the pipeline without the bin.

See the repo README for project-wide setup and examples/basic for a runnable consumer.

License

MIT