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

@fdekit/environment-docker

v0.4.6

Published

Docker Compose local environment package for FDEKit

Readme

@fdekit/environment-docker

Purpose

@fdekit/environment-docker describes and operates a local Docker Compose customer-like environment around an FDEKit deployment. It produces start/stop/seed commands, health checks, service evidence, and endpoint metadata for fdekit env * commands and dashboard/report evidence.

Use it for local container stacks such as customer APIs, databases, queues, caches, workers, or gateways.

Who should use this package

  • Deployment authors who need repeatable local customer-like infrastructure.
  • Recipe authors packaging Docker Compose setup alongside an agent workflow.
  • Contributors maintaining environment command generation and evidence metadata.

Choose a connector package when the agent needs to call a system. Choose this package when the operator needs to start, seed, check, or describe the system around the agent.

5-minute quick example

import { defineDeployment } from '@fdekit/core';
import { dockerEnvironment } from '@fdekit/environment-docker';

export default defineDeployment({
  name: 'support-triage-docker',
  environment: 'local',
  runtimeEnvironment: dockerEnvironment({
    composeFile: './docker-compose.local.yml',
    projectName: 'customer-support-stack',
    services: ['customer-api', 'postgres', 'redis'],
    customerApi: {
      serviceName: 'customer-api',
      url: process.env.CUSTOMER_API_URL ?? 'http://localhost:8787',
      healthUrl: 'http://localhost:8787/health',
    },
    seed: 'npm run seed:docker',
  }),
  providers: {
    mock: { name: 'mock' },
  },
  agents: {
    // ...
  },
});

Then run:

fdekit env start
fdekit env seed
fdekit env doctor
fdekit env describe

Public API surface

Import from the package root:

import { dockerEnvironment } from '@fdekit/environment-docker';
import type { DockerEnvironmentOptions, DockerEnvironmentDefinition } from '@fdekit/environment-docker';

Root exports include dockerEnvironment, Docker environment option/config/definition types, command helpers such as dockerComposeStartCommand, and Docker Compose utility types. The environment family is summarized in the public API index: Public API Reference.

Stability/backward-compat notes

@fdekit/environment-docker is public but pre-1.0. The package-root factory, option/config types, command names, environment kind local-docker, and evidence shape are compatibility-sensitive.

Subpath imports are internal. Keep this package operator-facing; agents should still call customer systems through connectors.

See also