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

create-isaacs

v2.3.0

Published

An npm init module to create modules like I do

Downloads

9

Readme

create-isaacs

An npm init module to create modules like I do.

$ npm init isaacs [module-name [description]] -- [flags...]

Flags

  • -y --yes Accept defaults from all prompts. (Note that defaults are not provided for certain git configs, so it'll still prompt for those. There is no guaranteed-headless mode, this is just a convenience to not have to mash the enter key so much.)
  • -a --always-yes Accept defaults now, and all future runs, until run with --no, which unsets it.
  • -n --no Do not accept defaults. (This takes precedence over --yes and unsets the --always-yes flag, even if it was set on this run.)
  • -e --default-export Set up a default export in the CommonJS interface.
  • -E --no-default-export Do not set up a default export in the CommonJS interface.
  • -EE --never-default-export Never set up a default export, in this or any future runs. (Removed by running with -ee or -e.)
  • -ee --always-default-export Set a default export, in this and all future runs. (Removed by running with -EE or -E.)
  • -b --bin set to avoid prompt if this module has a bin
  • -B --no-bin set to avoid prompt asking if pacage contains a bin.
  • -bb --always-bin set to avoid prompt if this module has a bin
  • -BB --never-bin set to avoid prompt asking if pacage contains a bin.

Examples:

# do all prompts, no matter what
npm init -- --no
# create the module with that name/description, accept all defaults
npm init isaacs -- @foo/bar "a bar in the foo namespace" --yes
# create the module with that name/desc, accept defaults forever
npm init isaacs -- xyzasdf 'just a dummy module' --always-yes

What It Do

This creates a hybrid TypeScript module, with tests set up to work using tap.

Default exports in CommonJS mode are supported if desired.

All source is in ./src, all tests in ./test.

Distribute to npm by running npm version <whatever>, and it'll publish and push to git automatically.

The engines field in package.json is automatically set up to restrict to the currently supported major node versions.

Uses the Blue Oak 1.0.0 license, a modern liberal non-copyleft written in understandable plain english.

A set of GitHub Actions workflows are included, which run tests against all currently supported node versions, and some other niceties to ensure that the repository field in package.json is set properly, and that any copyright notices in the license file have accurate years.

(Note: Blue Oak doesn't include a copyright statement, but if you switch to another license that does, then this will prevent some automated emails from various organizations.)