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

@jokeyrhyme/node-init

v4.0.0

Published

impose my will upon a new or existing Node.js project

Downloads

32

Readme

jokeyrhyme / node-init npm Travis CI Status

impose my will upon a new or existing Node.js project

Usage

npm install -g @jokeyrhyme/node-init

# use to start a fresh new project from scratch:
node-init my-project

# which is the equivalent of running:
mkdir my-project; cd my-project; node-init

# without a project name, assume current working directory:
node-init

# to find more details about usage
node-init --help

Options

--scope [scope]        set npm @scope prefix
--check-git-status     stop work if un-versioned changes
--no-check-git-status  do work even if un-versioned changes

What does this do?

Version Control

  • runs git init to start a git repository, if none is found

  • ensures there's a .gitignore file containing "node_modules"

NPM good-practices

  • runs npm init -y to start a package.json or to restore important missing fields to an existing package.json

  • ensures "name" in package.json includes desired scope (if any)

  • ensures "engines" is set in package.json, defaults to major versions of current npm and node

  • ensures all versions in "devDependencies" in package.json start with "^"

  • adds an NPM version badge to README.md if none is found, and the package is not marked as "private"

  • sets default { publishConfig: { access: 'public' } } in package.json if there is a scope

  • use sort-package-json to keep package.json tidy

  • package "main" refers to a file that exists (created for you, if not)

  • use nsp to check for vulnerable dependencies

Code Quality

  • installs and configures prettier and npm run prettier

  • installs and configures ESLint, with eslint-plugin-node

  • install and configure jest if other test frameworks are absent and npm test is not configured

  • adds an npm run eslint script for ESLint

  • installs and configures FlowType and npm run flow

  • uninstalls FlowType when not used

  • add npm run ava if using ava

  • add npm run jest if using jest

  • add npm run mocha if using mocha

  • add npm run nyc if using nyc

Continuous Integration

  • adds a Travis CI badge to README.md if none is found (GitHub-only)

  • ensures .travis.yml has good defaults at least (GitHub-only)

  • adds an AppVeyor badge to README.md if none is found (GitHub-only or Bitbucket-only)

  • ensures appveyor.yml has good defaults at least (GitHub-only or Bitbucket-only)

IDE / Code Editor settings

Other Opinionated Stuff

  • for simplicity, text files should use UNIX line-endings

  • install a project-local copy of npx, which is very useful for executing other CLI tools