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

@awsless/awsless

v0.0.404

Published

- add fargate container stuff for long lived services - add check for existing graphql resolver field in schema - add check for conflicting types inside graphql (Like duplicate type names) - Types should probably only allowed to defined once. And should

Downloads

1,473

Readme

TODO:

  • add fargate container stuff for long lived services
  • add check for existing graphql resolver field in schema
  • add check for conflicting types inside graphql (Like duplicate type names)
    • Types should probably only allowed to defined once. And should be extended after that.

BUGS

  • Container Lambda's don't update the lambda correctly when ever the container code updates.
  • GraphQL resolver code doesn't update correctly.
  • S3 bucket doesn't delete propertly when files are inside.
  • Cleanup unused network interfaces on VPC delete.
  • ECR Repo doesn't delete propertly when images are inside.



Features

  • VPC
  • Tests
  • Commands
  • Auth
  • Config
  • Domains
  • Sites
  • Functions
  • Tasks
  • Instances
  • Database
    • Tables
    • Stores
    • Caches
    • Searchs
  • Queues
  • Topics
  • Realtime
  • Crons
  • API
    • HTTP
    • GraphQL
  • Process Failure Capture

Domains

We use AWS Route53 to provide domain management.

{
  "domains": {
    "main": {
      "domain": "example.com",
      "dns": [{
        "name": "sub",
        "type": "A",
        "records": [ ... ],
      }]
    },
  }
}

Functions

We use AWS Lambda to provide serverless functions.

{
  "functions": {
  	"FUNCTION_NAME": "function.ts"
  }
}

Tasks

We use AWS Async Lambda to provide serverless async tasks. Tasks are an lower cost alternative to queues.

{
  "tasks": {
  	"TASK_NAME": "task.ts"
  }
}

Instances

We use AWS EC2 Instances to provide low level server instances. Tasks are an lower cost alternative to queues.

{
  "instances": {
  	"INSTANCE_NAME": {
	  "type": "t4g.nano",
	  "image": "ami-000000",
	  "code": "./src",
	  "command": "sh ./startup.sh",
	}
  }
}

Tables

We use AWS DynamoDB to provide serverless tables.

{
  "tables": {
    "TABLE_NAME": {
      "hash": "id",
      "fields": {
        "id": "number",
      }
    }
  }
}

Stores

We use AWS S3 to provide serverless key-value storage.

{
  "stores": [ "STORE_NAME" ]
}

Caches

We use AWS MemoryDB to provide a redis compatible in-memory storage.

{
  "caches": {
    "CACHE_NAME": {
      "type": "t4g.small"
    }
  }
}

Searchs

We use AWS Open Search to provide a serverless search api.

{
  "searchs": {
    "SEARCH_NAME": {
      "type": "t3.small"
    }
  }
}

Queues

We use AWS SQS to provide serverless queues.

{
  "queues": {
    "QUEUE_NAME": "queue-consumer.ts"
  }
}

Topics

We use AWS SNS to provide serverless pubsub topics.

{
  "topics": [ "TOPIC_NAME" ],
  "subscribers": {
    "TOPIC_NAME": "topic-consumer.ts",
  }
}

Realtime

We use AWS IoT to provide a serverless mqtt pubsub channel.

{
  "pubsub": {
    "PUBSUB_NAME": {
      "sql": "SELECT * FROM '$aws/events/presence/connected/+'",
      "consumer": "pubsub-consumer.ts",
    }
  }
}

Crons

We use AWS Event Bridge to provide serverless cron jobs.

{
  "crons": {
    "CRON_NAME": {
      "schedule": "1 day",
      "consumer": "cron-consumer.ts",
    }
  }
}

HTTP

We use AWS ELB to provide a HTTP API.

{
  "http": {
    "HTTP_API_NAME": {
      "GET /posts": "list-posts.ts",
      "POST /posts": "create-post.ts",
    }
  }
}

REST

We use AWS ApiGatewayV2 to provide a serverless REST API.

{
  "rest": {
    "REST_API_NAME": {
      "GET /posts/{id}": "get-posts.ts",
      "DELETE /posts/{id}": "delete-post.ts",
    }
  }
}

GraphQL

We use AWS AppSync to provide a serverless GraphQL API.

{
  "graphql": {
    "GRAPHQL_API_NAME": {
      "schema": "schema.gql",
      "resolvers": {
        "Query": {
          "posts": "list-posts.ts",
        },
        "Mutation": {
          "createPost": "create-post.ts",
        }
      }
    }
  }
}

Auth

We use AWS Cognito to provide a serverless Authentication API.

{
  "auth": {
    "AUTH_USER_POOL_NAME": {
   	  "allowUserRegistration": false,
   	  "password": {
   	    "minLength": 24
   	  }
    }
  }
}

Commands

You can define custom cli commands that you can run from the awsless cli tool.

{
  "commands": {
    "COMMAND_NAME": "./cli/your-command.ts"
  }
}