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

@arinoto/cdk-arch

v0.6.0

Published

CDK Architecture primitives for event-driven solution architectures

Readme

CDK Architecture

A set of CDK primitives that allow defining conceptual event-driven solution architectures. This allows to separate design and implementation (later done with CDKTF) of which there could be multiple - local, different clouds, etc; generate architecture diagrams and, most importantly this allows an easier refactoring of architectures and validation of implementations.

Something like this for a hello world that later can be implemented as an AWS ApiGateway with a lambda function and Dynamo, or an k8s microservice running in azure in Azure Database for PostgreSQL


export class ApiContainer extends Construct {...}
export class Function extends Construct {...}
export class JsonStore extends ApiContainer {...}

const arch = new Architecture();

const jsonStore = new JsonStore();

const api = new ApiContainer(arch, {
	'/v1/api/hello/{name}': new Function(arch, (name: string) => {
		jsonStore.store('greeted', {when: Date.now(), name});
		return `Hello, ${name}!`
	})
});

arch.synth()

After that we have C4's system or container definitions (which we can generate as diagrams) and can create a CDKTF definition for its deployment that will aditionally validate that all architectural components have corresponding deployment elements.