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

@thaitype/infra-state-matcher

v0.0.8

Published

Support Terraform State for Matching config between resources e.g. compare config between Active Site & DR Site

Readme

Infra State Matcher

Support Terraform State for Matching config between resources e.g. compare config between Active Site & DR Site

Only support bun runtime, for Node.js Runtime, please open the PR for fixing #!/usr/bin/env node shebang on scripts/insert-shebang.ts file which can able to load TypeScript file

Getting Started

Installation

npm install @thaitype/infra-state-matcher

Usage

  1. Export Terraform State into serialized JSON format on your terraform root module directory
    terraform show -json > prod.state.json
  2. Copy the JSON file to the directory where you want to run the matcher
    cp prod.state.json .state/prod.state.json
  3. Run build command to generate the matcher type helper, ism build
  4. Write a configuration file for matching resources between two Terraform states, see example in examples/simple.match.ts
    1. Import Type Helper from the generated file
    import type { State } from '../.gen/SimpleStateMatcher/types.js';
    1. Write your own class and inherit ResourceAnnotation class for declaring resources metadata for matching in test cases
    class SimpleResourceAnnotation extends ResourceAnnotation {
      public label(resources: GenericResourceAnnotation[]): GenericResourceAnnotation[] {
        // Write your logic here
        return resources;
      }
    }
    1. Write your own class and inherit StateMatcher class for matching resources between two Terraform states
    class SimpleStateMatcher extends StateMatcher {
      public match(): void {
        const matcher = new ConfigMatcher({
          defaultPair: {
            actual: { site: 'dr' },
            expected: { site: 'active' },
          },
        });
    
        // Starting matching the resource `azurerm_app_service` with the service `web` and scope `contractor`
        const contractorWeb = matcher.createResourceMatcher<State['azurerm_app_service.common_auth_gateway']>({
          resource_type: 'azurerm_app_service',
          service: 'web',
          scope: 'contractor',
        });
    
        contractorWeb.expectKey('values.app_settings.APPLICATIONINSIGHTS_CONNECTION_STRING').matchConstant('value');
      }
    }
    1. Config how the matcher should run in the main function
    export default new MatchRunner({
      annotation: SimpleResourceAnnotation,
      stateMather: SimpleStateMatcher,
      options: {
        stateFile: ".state/prod.state.json",
      },
    });
  5. Run start command to start the matching process, ism

Local Development

Development

bun install
bun run build

Type Checking

bun run check

Type Checking with Watch

bun run check:watch

Publish

Using release-it to publish the package, using npm commandline with OTP (One Time Password) for 2FA (Two Factor Authentication)

bun run release