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

@telegraph-notify/telegraph-cli

v1.0.1

Published

CLI tool for deploying Telegraph to AWS

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

kwjoleekwjoleefranceshgrayfranceshgrayerinrolsonerinrolsoncshiocshio

Keywords

Readme

Telegraph CLI

Table of Contents

Installation

Run the following command to install Telegraph CLI.

$ npm install -g @telegraph-notify/telegraph-cli

Getting Started

You must have aws-cli, aws-cdk, and git-cli installed to begin the initialization process. The installation status of these applications can be verified by running the following commands and getting back a file path.

$ which aws
$ which cdk
$ which git

An AWS account must have been created, along with an AWS IAM role with AdministratorAccess permissions. The access key and secret access key must have also been created on the Security Credentials page.

The AWS CLI must be configured by running the aws configure command. The account and region must be specified using the access keys created in the previous step.

Secret keys to be used in conjunction with the SDKs will be displayed after deployment in addition to URLs to the API gateways. Please save these as they are necessary to integrate Telegraph services.

To initialize Telegraph and ensure your environment is ready for deployment, run:

$ telegraph init

You will be prompted to enter an email address to be used as the sender's email for email notification, the application's secret key, and the API key for the dashboard. The secret key and API key can be left blank to automatically generate them.

Deploying to AWS

Telegraph is ready to be deployed to AWS after a successful initialization.

$ telegraph deploy

Note: The deployment of Telegraph can take about 10 minutes.

Tearing down Telegraph

To delete Telegraph from AWS, run:

$ telegraph destroy

Note: The removal of Telegraph can take about 10 minutes.

Changing the Secret Key

To change the secret key on AWS, run:

$ telegraph secretkey

Changing the Dashboard API Key

To change the dashboard API key on AWS, run:

$ telegraph apikey