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 🙏

© 2024 – Pkg Stats / Ryan Hefner

cloudformation-resources

v1.7.0

Published

Typed CloudFormation resource names for safety and auto-completion

Downloads

164

Readme

CloudFormation Resource Identifiers

I was tired of passing string values as CDK resource type identifiers in my TypeScript projects, so I scraped AWS's docs and built a class-based typeset of (a handful of) identifiers.

We have a type system; we can do better. Except for the project name: that bit remains completely terrible.

Installation

npm

npm i --save-dev cloudformation-resources

Yarn

yarn add --dev cloudformation-resources

Usage

In your CDK TypeScript files:

import { Template } from "aws-cdk-lib/assertions";
import { AWS } from "cloudformation-resources";

const app = newApp("dev");
const stack = new VpcStack(app, "vpc-stack", {});

const template = Template.fromStack(stack);
template.resourceCountIs(AWS.EC2.VPC, 1); // instead of the wholly-gnarly "AWS::EC2::VPC"

Alternatively, you can import just the service set:

import { EC2 } from "cloudformation-resources/ec2";

const app = newApp("dev");
const stack = new VpcStack(app, "vpc-stack", {});

const template = Template.fromStack(stack);
template.resourceCountIs(EC2.VPC, 1);

Building Typesets

Building (or re-building) the identifier sets requires Deno. To scrape the AWS docs and generate the TypeScript files, run:

deno run --allow-net --allow-write --allow-read scripts/scrape-identifiers.ts

Contributing

Pull requests are welcome. To add services, add them to servicePages in scripts/scrape-identifiers.ts, then run the build command.

[!IMPORTANT] Be sure to run deno fmt before committing to ensure consistent formatting.