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

reason-lang

v0.0.0

Published

## Project Structure The following folder structure will be generated. ```bash ├──infra # an AWS CDK application that deploys the repo's infrastructure ├──packages ├──service # the NPM package containing the my-service business logic ```

Downloads

1

Readme

Welcome to your Eventual Project

Project Structure

The following folder structure will be generated.

├──infra # an AWS CDK application that deploys the repo's infrastructure
├──packages
    ├──service # the NPM package containing the my-service business logic

infra

This is where you control what infrastructure is deployed with your Service, for example adding DynamoDB Tables, SQS Queues, or other stateful Resources.

packages/service

This is where you add business logic such as APIs, Event handlers, Workflows and Activities.

Deployed Infrastructure

After deploying to AWS, you'll have a single stack named ai-bank containing your Service. Take a look at the structure using the Resources view in CloudFormation. Here, you can find a list of all the Lambda Functions and other Resources that come with a Service.

See the Service documentation for more information.

Scripts

The root package.json contains some scripts for your convenience.

Build

The build script compiles all TypeScript (.ts) files in each package's src/ directory and emits the compiled output in the corresponding lib/ folder.

pnpm build

Test

The test script runs jest in all sub-packages. Check out the packages/service package for example tests.

pnpm test

Watch

The watch script run the typescript compiler in the background and re-compiles .ts files whenever they are changed.

pnpm watch

Synth

The synth script synthesizes the CDK application in the infra/ package.

pnpm synth

Deploy

The deploy script synthesizes and deploys the CDK application in the infra/ package to AWS.

pnpm run deploy

Hotswap

The hotswap script synthesizes and deploys the CDK application in the infra/ package to AWS using cdk deploy --hotswap which can bypass a slow CloudFormation deployment in cases where only the business logic in a Lambda Function has changed.

pnpm run deploy