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

scout-app-starter

v0.2.0

Published

### Development

Downloads

29

Readme

Scout Starter App

Development

Install dependencies:

npm install

Start development server:

npm start

Create production build:

npm run build

Lint JavaScript files:

npm run lint

Run unit tests:

npm test

Run unit tests in watch mode (tests will re-run when on file changes):

npm run test:watch

Run end-to-end tests:

npm run e2e

Run storybook:

npm run storybook

Delete build artifacts and reinstall dependencies:

npm run clean

Deployment

AWS

Before auto-provisioning your infrastructure, you'll need to create an AWS account

IAM User

In AWS, create a user in IAM for programmatic access, and attach the following policies to the user:

  • AmazonS3FullAccess
  • CloudFrontFullAccess

Once you've created the IAM user, copy the access key ID and secret access key into the corresponding fields within config.js.

S3 Bucket

In config.js, choose a valid AWS region and S3 bucket name that you will use to store your app's static files. Do not manually create the S3 bucket. It will be created for you.

Cloudfront

The Cloudfront distribution for your app will automatically be created during provisioning. Once provisioning is complete, your distribution's URL will be logged to the terminal with additional instructions for configuring your CloudFlare DNS records.

CloudFlare

Before auto-provisioning your infrastructure, you'll also need to create a CloudFlare account.

Once you've created a CloudFlare account and configured your nameservers for your domain, you'll need to add your account email, zone ID, and API key to config.js.


Provision AWS infrastructure:

npm run provision

Deploy to AWS:

npm run deploy