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

minni-module

v1.4.1

Published

Minimal npm module scaffolding

Downloads

39

Readme

minni-module

Minimal npm module scaffolding

Build Status Greenkeeper badge NSP Status JavaScript Style Guide semantic-release Commitizen friendly codecov

Work in progress

Not redy for usage yet.

Usage

  Example: 

    minni-module --name myModuleName --author myself 

  will create a new folder in current directory named 'myModuleName'
  and set myself as author in config file as a parammeter to parse templates.


  Options:
    -a  --author      Author name (package.json)                  [conf]
    -e  --email       email (code-of-conduct.md)                  [conf]
    -u  --user        Github user (urls in package.json)          [conf]
    -n  --name        Name of the module (folder, package.json)
    -d  --description Short description (README.md, package.json)

  All options marked as '[conf]' will be saved for future usage.
  You will see them in order to confirm on every use and can be overwriten
  in any invocation.

What it does

Scaffolds a high quality javascript module in one command so you can focus on codding.

Why

We love high quality open source so we love standards, best practices and unix filosophy.

The goal of this tool is to make it as uncomplicated as posible to create new healthy modules.

Let's make high quality our default.

Features

Static analysis

Check code for common mistakes and style on every commit with standard .

Security

Audit your dependencies for known vulnerabilities on every commit using nsp.

Tests

Write uncomplicated tests with tape and run your test suit on every commit.

Test coverage

Keep an eye on test coverage with istanbul.

Release

Rekease often and reliably with commitizen and semantic release.

Update

With all this in place it's really easy to enable greenkeeper to let it keep dependencies up to date for you.

Colaborate

Inform contributors and users about your workflow with issues and pull request templates.

Organize

Create a healthy community around your work by establishing a govenance model (open open-source) and a code of conduct (contributor covennant).

Write

Use write-good to to lint documentation.

$ npm run lint-prose

Certify

Your minni-module based module is almost ready to certify CII Best Practices.

Go get your badge to proudly show in the readme.