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

nodejs-project-example

v0.0.0-development

Published

Bare bones tools that should be used in every Node.js project.

Downloads

7

Readme

Node.js Project Example

Greenkeeper badge CirlceCI Badge Dependency Status devDependency Status Known Vulnerabilities semantic-release Commitizen friendly

Repository containing the bare bones tools I use in every Node.js project (yarn, flow, eslint, prettier, husky, flow, babel, jest, snyk, greenkeeper, circleci, semantic-release)

Requirements

  • Node.js (see .nvmrc for correct version).
  • Yarn
  • Greenkeeper.io configured to run on your repository.
  • CircleCI.com configured to run on your repository.

Setup

  • Clone this repository.
  • In this repository's root folder, run yarn.

Testing & Linting

This project uses Jest, ESlint with the AirBnb standard, and Prettier for testing, linting, and formatting.

  • All test files are suffixed with .test.js.
  • To run tests: yarn test.
  • To lint this codebase, run: yarn lint.
  • To format this codebase, run: yarn prettier.
  • To validate flow typing, run: yarn flow.
  • NOTE: lint and prettier will be run before a commit is made.

Building

To build this project, simply run yarn build.

Services and Integrations

This project contains CircleCI integration configuration. To get this working, do the following:

  • Sign up for a CircleCI account.
  • Add your project to Circle (Projects -> Add Project).
  • Add GH_TOKEN and NPM_TOKEN environment variables to your CircleCI project. (See this documentation for instructions on fetching those tokens).
  • Update CircleCI shield in this README to point to the correct repository.

To set up Greenkeeper, do the following:

  • Make sure you have CircleCI set up.
  • Sign up for a Greenkeeper account.
  • Add your project repository to Greenkeeper.
  • Merge the initial Greenkeeper pull request.
  • Update greenkeeper, dependencies, and devDependencies shields in this README to point to the correct repository.

To set up Snyk

  • Sign up for a Snyk.io account.
  • Enable Snyk for your repository.
  • Update Snyk shield in this README to point to the correct repository.

Automated Releases

To enable automated releases to NPM via semantic release, replace the semantic-release command in your package.json file with the following:

...
  "semantic-release": "semantic-release pre ; npm publish ; semantic-release post",
...

This project isn't published to NPM, this step simply adds npm publish between semantic-release pre/post commands.