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

daft-conf

v0.1.1

Published

Stupidly simple nodejs config management

Downloads

2

Readme

Bulletproof Nodejs Boilerplate

Package version Travis build status License: Unlicense Coverage Status PRs Welcome NPS Security Check Share on Twitter

Lean, and functional boilerplate to get you started with creating a nodejs app. You have ES6/7, corresponding linting rules, a debugging config for vscode, Jest test runner.

No tie-up with any plugins like Express and the likes. It's a barebones NodeJS app with live-reload, testing, test-coverage and a simple TravisCI build.

It is also a good base for your node or CLI apps and is designed to be:

  • Compatible with latest LTS of node, but backwards compatible with Node 6 (you'll need to run yarn run start:legacy)
  • Forward-thinking (async / await / object spreads and the likes)
  • Debuggable (includes vscode debug config)
  • Testable (check out the test file to see cool async tests)
  • CI ready (Travis config included)
  • NVM-friendly (see .nvmrc)

Developer goodies

  • .editorconfig
  • relateable linting rules
  • tests & test coverage
  • create-nodejs-app cli tool (WIP)
  • live-reload when you save a file.

Get started

There are three ways of using this boilerplate.

  1. Download the release and extract

  2. Clone the repo without it's history:

    # clone this repo
    git clone --depth=1 --branch=master https://github.com/piggyslasher/bulletproof-node-boilerplate.git youNewProject
    
    rm -rf !$/.git #removes the .git directory
  3. Use the create-nodejs-app (in progress :)

To start the app

# To just run the script and see output
npm start # or
yarn start

# for development and live-reload
npm run start:watch #or
yarn run start:watch

Debug in VSCode

Debug using VSCode

Using nvm? Got you covered

Debug with nvm version in .nvmrc

Progress Tracker

  • [ ] use create-new-cli to provision node app
  • [X] maintain node version compatibility
    • [X] Latest LTS
    • [X] Node 6+
  • [X] perform live-reload of all scripts using nodemon
  • [X] provide testing using Jest
  • [X] provide TravisCI basic testing
  • [X] provide codacy stats
  • [X] provide code coverage
  • [X] provide sane linting rules (currently based on Airbnb but allows goodies like dangling commas and semi-colon-free development)
  • [X] use async/await/promisify
  • [X] support CLI tools (have a look at bin/cli.js)
  • [ ] allow options for 3rd party linting rules (standard, airbnb)
  • [X] debug using vscode's node debugger
    • [ ] use babel sourcemaps during debgging (workaround, use debugger)