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

@sharyn/cli

v4.7.8

Published

[![npm](https://img.shields.io/npm/v/@sharyn/cli.svg)](https://www.npmjs.com/package/@sharyn/cli)

Downloads

52

Readme

🌹 @sharyn/cli

npm

This package provides CLI tasks to use as your NPM scripts.

🌹 Install

npx install-peerdeps -o -Y @sharyn/cli-peer-deps && npx install-peerdeps -o -Y -d @sharyn/cli-peer-devdeps && yarn add @sharyn/cli

🌹 Usage

In your package.json, add the following scripts:

  "scripts": {
    "start": "sharyn dev",
    "ssr-only": "sharyn dev-ssr-only",
    "no-ssr": "sharyn dev-no-ssr",
    "local-prod": "sharyn local-prod",
    "lint": "sharyn lint",
    "test": "sharyn test",
    "stats": "sharyn stats",
    "heroku-postbuild": "sharyn build-prod"
  },

And if you have Husky:

  "husky": {
    "hooks": {
      "pre-commit": "sharyn lint-test"
    }
  },

🌹 Tasks

dev

Runs sequencially:

  • If a docker-compose.yml file is present:
    • docker-compose up -d
  • If a knex-config.js file is present at src/_db/knex-config.js or provided via @sharyn/db:
    • until docker run --rm --link db:pg --net sharyn-net postgres:latest pg_isready -U postgres -h pg; do sleep 1; done
    • knex --knexfile [path-to-knex-config.js] --cwd . migrate:latest
    • If a src/_db/seeds folder is present:
      • knex --knexfile [path-to-knex-config.js] --cwd . seed:run
  • rimraf dist/js/bundle.js

Then runs in parallel:

  • nodemon -w src -i dist -x "babel-node src/_server/server.js"
  • webpack-dev-server --mode=development --progress --hot [--config node_modules/[@]sharyn/webpack-config if [@]sharyn/webpack-config installed]

dev-ssr-only

Runs sequencially:

  • If a docker-compose.yml file is present:
    • docker-compose up -d
  • If a knex-config.js file is present at src/_db/knex-config.js or provided via @sharyn/db:
    • until docker run --rm --link db:pg --net sharyn-net postgres:latest pg_isready -U postgres -h pg; do sleep 1; done
    • knex --knexfile [path-to-knex-config.js] --cwd . migrate:latest
    • If a src/_db/seeds folder is present:
      • knex --knexfile [path-to-knex-config.js] --cwd . seed:run
  • cross-env SSR_ONLY=true nodemon -w src -i dist -x "babel-node src/_server/server.js"

dev-no-ssr

Runs sequencially:

  • If a docker-compose.yml file is present:
    • docker-compose up -d
  • If a knex-config.js file is present at src/_db/knex-config.js or provided via @sharyn/db:
    • until docker run --rm --link db:pg --net sharyn-net postgres:latest pg_isready -U postgres -h pg; do sleep 1; done
    • knex --knexfile [path-to-knex-config.js] --cwd . migrate:latest
    • If a src/_db/seeds folder is present:
      • knex --knexfile [path-to-knex-config.js] --cwd . seed:run
  • rimraf dist/js/bundle.js

Then runs in parallel:

  • cross-env NO_SSR=true nodemon -w src -i dist -x "babel-node src/_server/server.js"
  • webpack-dev-server --mode=development --progress --hot [--config node_modules/[@]sharyn/webpack-config if [@]sharyn/webpack-config installed]

local-prod

Runs sequencially:

  • If a docker-compose.yml file is present:
    • docker-compose up -d
  • If a knex-config.js file is present at src/_db/knex-config.js or provided via @sharyn/db:
    • until docker run --rm --link db:pg --net sharyn-net postgres:latest pg_isready -U postgres -h pg; do sleep 1; done
    • knex --knexfile [path-to-knex-config.js] --cwd . migrate:latest
    • If a src/_db/seeds folder is present:
      • knex --knexfile [path-to-knex-config.js] --cwd . seed:run
  • rimraf lib dist/js/bundle.js
  • cross-env NODE_ENV=production webpack --mode=production --progress [--config node_modules/[@]sharyn/webpack-config if [@]sharyn/webpack-config installed]
  • babel src -d lib
  • If a Procfile file is present:
    • cross-env NODE_ENV=production heroku local
  • If not:
    • node lib/_server/server.js

build-prod

Runs sequencially:

  • rimraf lib dist/js/bundle.js
  • cross-env NODE_ENV=production webpack --mode=production --progress [--config node_modules/[@]sharyn/webpack-config if [@]sharyn/webpack-config installed]
  • babel src -d lib

migrate-db

Runs knex --knexfile [path-to-knex-config.js] --cwd . migrate:latest

With [path-to-knex-config.js] being src/_db/knex-config.js or the one provided by @sharyn/db

Useful for the release command in Heroku's Procfile or on its own during local development.

lint

Runs sequencially:

  • eslint src
  • flow

test

Runs sequencially:

  • If a docker-compose.yml file is present:
    • If a Docker process is found matching the db-test name:
      • docker rm -f [db-test-id]
    • docker-compose up -d db-test
  • If a knex-config.js file is present at src/_db/knex-config.js or provided via @sharyn/db:
    • until docker run --rm --link db-test:pg --net sharyn-net postgres:latest pg_isready -U postgres -h pg; do sleep 1; done
    • cross-env NODE_ENV=test knex --knexfile [path-to-knex-config.js] --cwd . migrate:latest
  • jest --testMatch **/*.unit.test.js [--globalSetup ./src/_testing/global-setup.js --globalTeardown ./src/_testing/global-teardown.js if these files exist]
  • cross-env NODE_ENV=production webpack --mode=production --progress [--config node_modules/[@]sharyn/webpack-config if [@]sharyn/webpack-config installed]
  • jest --preset jest-puppeteer --testMatch **/*.e2e.test.js --runInBand [--globalSetup ./src/_testing/global-setup.js --globalTeardown ./src/_testing/global-teardown.js if these files exist]

lint-test

Runs sequencially:

  • eslint src
  • flow
  • If a docker-compose.yml file is present:
    • If a Docker process is found matching the db-test name:
      • docker rm -f [db-test-id]
    • docker-compose up -d db-test
  • If a knex-config.js file is present at src/_db/knex-config.js or provided via @sharyn/db:
    • until docker run --rm --link db-test:pg --net sharyn-net postgres:latest pg_isready -U postgres -h pg; do sleep 1; done
    • cross-env NODE_ENV=test knex --knexfile [path-to-knex-config.js] --cwd . migrate:latest
  • jest --testMatch **/*.unit.test.js [--globalSetup ./src/_testing/global-setup.js --globalTeardown ./src/_testing/global-teardown.js if these files exist]
  • cross-env NODE_ENV=production webpack --mode=production --progress [--config node_modules/[@]sharyn/webpack-config if [@]sharyn/webpack-config installed]
  • jest --preset jest-puppeteer --testMatch **/*.e2e.test.js --runInBand [--globalSetup ./src/_testing/global-setup.js --globalTeardown ./src/_testing/global-teardown.js if these files exist]

Useful as the precommit Git hook or on its own.

stats

  • cross-env NODE_ENV=production webpack --mode=production --progress --json [--config node_modules/[@]sharyn/webpack-config if [@]sharyn/webpack-config installed] > webpack-stats.json