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

texit-constructs

v0.0.193

Published

This package exposes constructs to deploy texit as a serverless application to AWS.

Downloads

117

Readme

Texit Constructs

This package exposes constructs to deploy texit as a serverless application to AWS.

Usage

Two types of resources are exposed here, stacks and constructs. A typicaly installation can just import the stacks as default and deploy them. If you want a custom installation, all the resources have constructs exposed and you can use them to build your own stacks. To see an example deployment, see the serverless example in the main texit repo.

You need to supply a path to the binaries of the applications you are deploying due to limitations with CDK. Its is recommended to just grab them from a release and when creating a resource, just point to the path you downloaded them to.

Configs to run the binaries are expected to be in an S3 bucket. The bucket name and the path to the config file are expected to be passed as parameters to the resources.