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 🙏

© 2025 – Pkg Stats / Ryan Hefner

cdk-from-cfn

v0.258.0

Published

Turn AWS CloudFormation templates into AWS CDK applications

Readme

cdk-from-cfn

cdk-from-cfn is a command-line tool that converts AWS CloudFormation templates into AWS CDK code. It supports multiple programming languages including TypeScript, Python, Java, Go, and C#.

Installation

cargo install cdk-from-cfn

Usage

cdk-from-cfn [INPUT] [OUTPUT] --language <LANGUAGE> --stack-name <STACK_NAME>
  • INPUT is the input file path (STDIN by default).
  • OUTPUT is the output file path; if not specified, output will be printed on your command line (STDOUT by default).

Node.js Module Usage

cdk-from-cfn leverages WebAssembly (WASM) bindings to provide a cross-platform npm module, which exposes apis to be used in Node.js projects. Simply take a dependency on cdk-from-cfn in your package.json and utilize it as you would a normal module. i.e.

import * as cdk_from_cfn from 'cdk-from-cfn';

// get supported languages
cdk_from_cfn.supported_languages();

// transmute cfn template into cdk app
cdk_from_cfn.transmute(template, language, stackName)

Language and Feature support

| Name | Enabled by default | Description | | ------------ | :----------------: | ------------------------------------- | | typescript | :heavy_check_mark: | Enables support for TypeScript output | | golang | :heavy_check_mark: | Enables support for Go output | | java | :heavy_check_mark: | Enables support for Java output | | Python | :heavy_check_mark: | Enables support for Python output | | csharp | :heavy_check_mark: | Enables support for C# output |

You can enable experimental languages (not enabled by default) by enabling the relevant feature:

$ cargo build --release --features=<feature-name>
Finished release [optimized] target(s) in 0.17s

If you want to disable on-by-default languages, you can pass --no-default-features:

$ cargo build --release --no-default-features --features=golang
Finished release [optimized] target(s) in 0.17s

Implemented

  • [x] Fn::FindInMap
  • [x] Fn::Join
  • [x] Fn::Sub
  • [x] Ref
  • [x] Fn::And
  • [x] Fn::Equals
  • [x] Fn::If
  • [x] Fn::Not
  • [x] Fn::Or
  • [x] Fn::GetAtt
  • [x] Fn::Base64 support
  • [x] Fn::ImportValue support
  • [x] Fn::Select support
  • [x] Resource ordering based on dependencies
  • [x] Conditions are emitted in ts but not attached to resource conditions
  • [x] Metadata emission for updates to asgs / lambda functions.
  • [x] Emission of outputs / exports
  • [x] Fn::GetAZs support
  • [x] Adding depends-on, and ordering based on it too.
  • [x] Deletion policy
  • [x] Fn::Cidr support

Remaining

There are known unsupported features. Working on them in priority order:

  • [ ] Create policy
  • [ ] ssm metadata references
  • [ ] secretsmanager references