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

@emulsify/cli

v1.11.4

Published

Command line interface for Emulsify

Downloads

2,389

Readme

Emulsify Design System npm

emulsify-cli

Command line interface for Emulsify.

Installation

This project is deployed to npm. In order to use this CLI, install it as a global dependency:

npm install -g @emulsify/cli

Usage

For more information on how to use emulsify-cli, please see the usage documentation.

Development

Emulsify-cli is developed using TypeScript. You can find all of the source files in the src directory, which is organized in the following manner:

  • src/index.ts - uses Commander to compose the CLI.
  • src/handlers - contains all functions that handle CLI commands, such as emulsify init.
  • src/lib - general definitions and logging tools.
  • src/schemas - contains JSON-Schema files that describe project, system, and variant configuration. These schema files are used to generate TypeScript types.
  • src/scripts - holds utility scripts for the project.
  • src/types - type modules live here, auto-generated ones are prefixed with an underscore (_).
  • src/util - contains utility functions that are used in handlers to do various things, such as caching systems.

Setup

  • Install the version of node as specified in this project's .nvmrc file. If you are using nvm, simply run nvm use.
  • Clone this repository into a directory of your choosing.
  • In the directory, run npm install.
  • Build the project: npm run build, or watch: npm run watch.
  • To test the CLI, run: npm link.

Scripts

  • npm run build: builds the project based on the configuration in tsconfig.dist.json.
  • npm run build-schema-types: Compiles the json-schema definitions within this project into ts types.
  • npm run watch: watches the codebase, and re-compiles every time a change is made.
  • npm run format: uses prettier to format all ts files within the codebase.
  • npm run lint: uses eslint to lint the codebase.
  • npm run test: runs Jest on the codebase. You can specify a path to a single test, and add any flags supported by Jest's CLI.
  • npm run type: uses typescript to check all type signatures.
  • npm run twatch: runs Jest without coverage, in verbose and watch mode. This is useful for running a single test during active development.

Deployment

This project is automatically built and deployed to NPM via a GitHub Actions workflow. In order to deploy changes merged into the develop branch, simply merge develop into main, and call it a day.

Contributors