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

@storm-software/pulumi-tools

v0.22.97

Published

Tools for managing Pulumi infrastructure within a Nx workspace.

Readme

Version Nx NextJs Commitizen friendly Semantic-Release documented with Fumadocs GitHub Workflow Status (with event)

[!IMPORTANT] This repository, and the apps, libraries, and tools contained within, is still in it's initial development phase. As a result, bugs and issues are expected with it's usage. When the main development phase completes, a proper release will be performed, the packages will be available through NPM (and other distributions), and this message will be removed. However, in the meantime, please feel free to report any issues you may come across.

Table of Contents

Storm Pulumi Tools

A package containing tools and base classes for the Pulumi Infrastructure as Code package to be used in a Storm workspace. It includes various Nx generators and executors for common development tasks.

This library was generated with Nx.

Installing

Using pnpm:

pnpm add -D @storm-software/pulumi-tools
npm install -D @storm-software/pulumi-tools
yarn add -D @storm-software/pulumi-tools

Executors

The following executors are available in this package to invoke common tasks for the workspace's projects:

Pulumi config Command Executor

Run the `config` command using the workspaces Pulumi IoC CLI

Example

This executor can be used by executing the following in a command line utility:

nx run my-project:config

Please note: The config executor should be included in the desired projects's project.json file.All required options must be included in the options property of the json.

Options

The following executor options are available:

| Option | Type | Description | Default | | --------- | ------ | ------------- | --------- | | stack | string | The target stack to use, if specified. | | | root | string | The working directory to run Pulumi commands from, if specified. | | | action * | string | | | | path | boolean | | | | secret | boolean | | | | name | string | | | | value | string | | |

Please note: Option names followed by * above are required, and must be provided to run the executor.

Pulumi import Command Executor

Run the `import` command using the workspaces Pulumi IoC CLI

Example

This executor can be used by executing the following in a command line utility:

nx run my-project:import

Please note: The import executor should be included in the desired projects's project.json file.All required options must be included in the options property of the json.

Options

The following executor options are available:

| Option | Type | Description | Default | | --------- | ------ | ------------- | --------- | | stack | string | The target stack to use, if specified. | | | root | string | The working directory to run Pulumi commands from, if specified. | | | target * | string | | | | name | string | | | | id * | string | | |

Please note: Option names followed by * above are required, and must be provided to run the executor.

Pulumi preview Command Executor

Run the `preview` command using the workspaces Pulumi IoC CLI

Example

This executor can be used by executing the following in a command line utility:

nx run my-project:preview

Please note: The preview executor should be included in the desired projects's project.json file.

Options

The following executor options are available:

| Option | Type | Description | Default | | --------- | ------ | ------------- | --------- | | stack | string | The target stack to use, if specified. | | | root | string | The working directory to run Pulumi commands from, if specified. | | | expectNoChanges | boolean | | |

Pulumi refresh Command Executor

Run the `refresh` command using the workspaces Pulumi IoC CLI

Example

This executor can be used by executing the following in a command line utility:

nx run my-project:refresh

Please note: The refresh executor should be included in the desired projects's project.json file.All required options must be included in the options property of the json.

Options

The following executor options are available:

| Option | Type | Description | Default | | --------- | ------ | ------------- | --------- | | stack | string | The target stack to use, if specified. | | | root | string | The working directory to run Pulumi commands from, if specified. | | | skipPreview * | boolean | A boolean flag to skip the preview step. | | | yes * | boolean | A boolean flag to automatically approve the refresh. | |

Please note: Option names followed by * above are required, and must be provided to run the executor.

Pulumi up Command Executor

Run the `up` command using the workspaces Pulumi IoC CLI

Example

This executor can be used by executing the following in a command line utility:

nx run my-project:up

Please note: The up executor should be included in the desired projects's project.json file.All required options must be included in the options property of the json.

Options

The following executor options are available:

| Option | Type | Description | Default | | --------- | ------ | ------------- | --------- | | stack | string | The target stack to use, if specified. | | | root | string | The working directory to run Pulumi commands from, if specified. | | | skipPreview * | boolean | A boolean flag to skip the preview step. | | | yes * | boolean | A boolean flag to automatically approve the `up` command. | | | suppressOutputs * | boolean | A boolean flag to suppress outputs in the `up` command. | | | json * | boolean | A boolean flag to output the `up` command as JSON. | |

Please note: Option names followed by * above are required, and must be provided to run the executor.

Generators

The following generators are available with this package to assist in workspace management:

Init Storm Pulumi Tools Plugin

Init Storm Pulumi Tools Plugin.

Options

The following executor options are available:

| Option | Type | Description | Default | | --------- | ------ | ------------- | --------- | | name * | string | | | | tags | string | Add tags to the project (used for linting) | | | directory | string | A directory where the project is placed | | | provider | string | Your cloud provider | |

Please note: Option names followed by * above are required, and must be provided to run the executor.

Building

Run nx build pulumi-tools to build the library.

Running unit tests

Run nx test pulumi-tools to execute the unit tests via Jest.

Storm Workspaces

Storm workspaces are built using Nx, a set of extensible dev tools for monorepos, which helps you develop like Google, Facebook, and Microsoft. Building on top of Nx, the Open System provides a set of tools and patterns that help you scale your monorepo to many teams while keeping the codebase maintainable.

Roadmap

See the open issues for a list of proposed features (and known issues).

Support

Reach out to the maintainer at one of the following places:

License

This project is licensed under the Apache License 2.0. Feel free to edit and distribute this template as you like.

See LICENSE for more information.

Changelog

This project adheres to Semantic Versioning. Every release, along with the migration instructions, is documented in the CHANGELOG file

Contributing

First off, thanks for taking the time to contribute! Contributions are what makes the open-source community such an amazing place to learn, inspire, and create. Any contributions you make will benefit everybody else and are greatly appreciated.

Please try to create bug reports that are:

  • Reproducible. Include steps to reproduce the problem.
  • Specific. Include as much detail as possible: which version, what environment, etc.
  • Unique. Do not duplicate existing opened issues.
  • Scoped to a Single Bug. One bug per report.

Please adhere to this project's code of conduct.

You can use markdownlint-cli to check for common markdown style inconsistency.

Contributors

Thanks goes to these wonderful people (emoji key):

This project follows the all-contributors specification. Contributions of any kind welcome!

Storm Software is an open source software development organization and creator of Acidic, StormStack and StormCloud.

Our mission is to make software development more accessible. Our ideal future is one where anyone can create software without years of prior development experience serving as a barrier to entry. We hope to achieve this via LLMs, Generative AI, and intuitive, high-level data modeling/programming languages.

Join us on Discord to chat with the team, receive release notifications, ask questions, and get involved.

If this sounds interesting, and you would like to help us in creating the next generation of development tools, please reach out on our website or join our Slack channel!