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

@aws-blocks/pipeline

v0.2.2

Published

CDK Pipelines-based CI/CD construct for AWS Blocks applications

Readme

@aws-blocks/pipeline

CDK Pipelines-based CI/CD construct for AWS Blocks applications.

Creates one self-mutating CodePipeline V2 per branch. Each pipeline:

  • Pulls source from GitHub via AWS CodeConnections (OAuth, no tokens)
  • Runs a synth step (install + cdk synth)
  • Self-mutates if the pipeline definition changes
  • Deploys to ordered stages with optional manual approval and bake time

Usage

import { Pipeline } from '@aws-blocks/pipeline';

new Pipeline(stack, 'Pipeline', {
  source: {
    repo: 'my-org/my-app',
    connectionArn: 'arn:aws:codeconnections:us-east-1:123456789012:connection/abc',
  },
  branches: [
    {
      branch: 'main',
      stages: [
        { name: 'beta' },
        { name: 'prod', requireApproval: true, config: { domain: 'myapp.com' } },
      ],
    },
  ],
  stageFactory: (scope, stageConfig) => {
    new MyAppStack(scope, 'App', { env: stageConfig.env });
  },
});

For async stage factories (for example, BlocksStack.create()), use the static Pipeline.create() method instead of new Pipeline().

Per-stage post-deploy steps (postStage)

The optional postStage prop runs a second per-stage phase after a stage deploys — for example a step that consumes the stage's deploy outputs. It is invoked once per deploy stage and returns steps that are attached as that stage's post-deploy actions:

import { Duration } from 'aws-cdk-lib';
import { CodeBuildStep } from 'aws-cdk-lib/pipelines';

new Pipeline(stack, 'Pipeline', {
  source: { repo: 'my-org/my-app', connectionArn: '...' },
  branches: [{ branch: 'main', stages: [{ name: 'beta' }, { name: 'prod', bakeTime: Duration.minutes(10) }] }],
  stageFactory: (scope, stageConfig) => new MyAppStack(scope, 'App', { env: stageConfig.env }),
  postStage: ({ stage, stageConfig, source }) => [
    new CodeBuildStep(`Smoke-${stageConfig.name}`, {
      input: source, // the resolved pipeline source — see below
      env: { STAGE: stageConfig.name },
      commands: ['npm ci', 'npm run smoke'],
    }),
  ],
});

The hook receives a PostStageContext:

  • stage — the CDK Stage the returned steps attach to.
  • stageConfig — the full stage config, including env (the stage's target account/region); read it to make a post step target the same account/region.
  • source — the resolved pipeline source file set for this stage's branch. Use it as a step's input so the step runs against the already-checked-out source. This is exposed precisely so a caller never has to walk the construct tree and string-match internal stage IDs to rediscover the source (which silently breaks on any internal rename).

Ordering with bakeTime. When a stage has both postStage steps and a bakeTime, the bake step is made to depend on the post-stage steps, so baking begins only after they complete rather than racing them in parallel. Returning undefined (or []) adds nothing and leaves synthesis identical to a pipeline with no hook.

Controlling the synth runtime

The synth step's CodeBuild runtime can be customized via synth.partialBuildSpec. It accepts three forms:

  • Omitted (undefined): the synth step declares Node.js 22 as the runtime. This is the default and recommended path.
  • null: explicit opt-out. No partialBuildSpec is injected, so the synthesized buildspec contains no runtime-versions block. Use this to bring your own runtime (for example via synth.installCommands) or to rely on the build image's built-in runtime.
  • A BuildSpec: used as-is, replacing the Node.js 22 default.

Pin a specific Node.js version

import { BuildSpec } from 'aws-cdk-lib/aws-codebuild';

new Pipeline(stack, 'Pipeline', {
  // ...
  synth: {
    partialBuildSpec: BuildSpec.fromObject({
      phases: { install: { 'runtime-versions': { nodejs: 20 } } },
    }),
  },
});

Opt out of the Node.js 22 default

Pass null to suppress the injected runtime entirely and manage it yourself:

new Pipeline(stack, 'Pipeline', {
  // ...
  synth: {
    partialBuildSpec: null,
    installCommands: ['n 20'], // or rely on the build image's default runtime
  },
});