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

@culturehq/scripts

v6.0.2

Published

A collection of scripts for JavaScript and TypeScript development

Downloads

95

Readme

@culturehq/scripts

Build Status Package Version

CultureHQ's CLI toolbox for JavaScript projects.

Usage

You install this module as a dev dependency in your package, as in:

yarn add --dev @culturehq/scripts

From there you can invoke any of the scripts listed in src/scripts by running chq-scripts [script]. You can add these to your package.json by adding to the scripts key, as in:

{
  "scripts": {
    "lint": "chq-scripts lint",
    "test": "chq-scripts test"
  }
}

The scripts themselves are listed below:

lint

Runs eslint with the @culturehq/eslint-config base configuration.

If you want to override the configuration, you can do all of the normal eslint config patterns of either creating a .eslintrc file, a .eslintrc.js file, putting a eslintConfig prop in your package.json, or passing the --config flag on the command line.

To make sure you're extending the config for this project, make sure you add extends: ["@culturehq"] to your config. If there are conflicts with your version of eslint, it's possible this config will be nested under the @culturehq/scripts directory, in which case you would need to add extends: ["./node_modules/@culturehq/scripts/node_modules/@culturehq/eslint-config"] to your config.

test

Runs jest with a pre-built configuration from src/config/jestConfig.js.

If you need to do something special at the beginning of the tests, chq-scripts supports adding a setupTests.js file at the root of the repository which will be automatically run before jest starts.

Development

Ensure you have node and yarn installed on your system. Then run yarn in the root of the repository to install the dependencies. Tests are run with yarn test and linting is run with yarn lint.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/CultureHQ/scripts.

License

The code is available as open source under the terms of the MIT License.