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

utils-addresses

v1.1.14

Published

demo npm module

Downloads

1

Readme

nqm-project-template

A starting template for all nqminds projects, apps, and databots, with eslint and vs code intellisense support

introduction

Configuring VS Code to get the maximum benefit from it's intellisense and linting capabilities can be a non-intuitive process. This guide aims to outline the basic steps required to get up and running.

eslint

eslint greatly helps in finding and avoiding bugs in your code, and will also help to make the nqminds code-base consistent rather than varying with each person's style.

eslint highlights (with a red squiggly line) possible bugs and inconsistent styling, and the following image shows eslint in action.

eslint

The following rules are imposed by the nqminds eslint configuration. It's not a long list and most of them are obvious and will greatly reduce the chance of bugs in your code if you adhere to them. Some of the style choices, e.g. double quotes rather than single quotes are subjective, but it's a case of choosing one and sticking to it for consistencies sake.

  • can't assign to a const variable
  • all variables must be defined before use
  • unreachable code is highlighted
  • all declared but unused variables are highlighted
  • must use === in place of ==
  • indents must be 2 spaces
  • all quotes must be double, not single
  • semi-colons must be used everywhere

No pull requests will be merged without a clean eslint report!

install

Install the eslint package globally on your machine.

sudo npm install -g eslint

You may also want to install and enable any plugins:

sudo npm install -g eslint-plugin-react

Install the VS Code eslint extension.

Copy the .eslintrc.json file from this repository to the root of your project folder.

intellisense

VS Code has some intellisense support out-of-the-box, but in order to get maximum benefit from it requires a few extra steps.

The following image shows full intellisense support for the lodash library:

intellisense

install

Install the typescript typings system.

sudo npm install -g typings

Copy the typings.json and jsconfig.json files from this repository to the root of your project folder.

Install the default node and lodash typings:

cd /path/to/project/root
typings install

Locate and install any other typings your project might need, e.g. Meteor:

typings search Meteor
typings install --save --global dt~meteor 

There is a full description of the VS Code typings system.