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

@opalesce/config

v0.0.1

Published

Typed project configuration for Opalesce

Downloads

284

Readme

@opalesce/config

@opalesce/config defines the project-facing configuration consumed by opalesce generate. It provides TypeScript inference without loading files, running plugins, writing artifacts, or changing process state. Normal projects access this API through opalesce or opalesce/config.

Project Config

Create one supported config file, normally opalesce.config.ts:

import { defineConfig, definePlugin } from "opalesce";

const metadata = definePlugin(() => ({
  name: "metadata",
  build(context) {
    context.emit({
      path: "metadata/version.txt",
      contents: `${context.document.version()}\n`,
    });
  },
}));

export default defineConfig({
  input: "./asyncapi.yaml",
  output: {
    path: "./generated",
    clean: true,
  },
  plugins: [metadata()],
});

Config-declared input and output paths resolve from the config file directory. The CLI resolves positional input and --out overrides from the invocation directory.

Configuration

interface OpalesceConfig {
  readonly input: string;
  readonly output: {
    readonly path: string;
    readonly clean?: boolean;
  };
  readonly parser?: ParseAsyncAPIOptions;
  readonly plugins?: readonly OrchestrationPlugin[];
}
  • input is one local AsyncAPI file path.
  • output.path is the generated artifact directory.
  • output.clean defaults to false. When enabled, the CLI accepts cleanup only for a safe directory below the config directory.
  • parser is forwarded to the in-memory engine in @opalesce/core.
  • plugins contains orchestration plugin instances.

defineConfig returns the same object and exists only to preserve concrete TypeScript inference.

Boundaries

This package does not discover or import config files, read the AsyncAPI input, run the pipeline, write artifacts, or expose a command. Those responsibilities belong to @opalesce/cli.

Config modules are trusted project code and execute normal JavaScript when the CLI imports them.

The scoped package is an internal workspace boundary. Project consumers install the opalesce facade instead of declaring @opalesce/config directly.