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

formatting-test

v0.1.1

Published

A collection of tests ready to ensure good formatting in your JS projects.

Downloads

1

Readme

formatting-test

THIS PACKAGE IS NO LONGER MAINTAINED

The formatting-test npm package helps JS developers test that their code meets certain formatting conventions. You can enable and disable rules as you choose, but you can't define your own rules. If you'd like to add any rules or functionality, I'm happy to accept PRs!

Installation

  1. Install the package
npm install -D mocha # if it's not already installed
npm install -D formatting-test
  1. Create formatting-test.js
const FormattingTest = require('./app');

new FormattingTest()
    .useAll() // by default, no rules are enabled
    .exec();
  1. Create an npm script (in package.json)
...
scripts: {
   "test-formatting": "mocha --reporter spec formatting-test.js",
},
...
  1. Run it
npm run test-formatting

Configuration

Enabling and disabling rules

By default, no rules are enabled. It's up to you to opt in to the rules you want to use. Alternatively, you can opt in to all rules and then out of any that you don't like.

Opting out of all rules (default behaviour, unless you've somehow overridden it)

new FormattingTest()
    .dontUseAll()
    .exec();

Opting in to all rules

new FormattingTest()
    .useAll()
    .exec();

Opting in to specific rules

new FormattingTest()
    .use(ruleName) // e.g. ruleName = 'dotConstructorIsNotUsed'
    .exec();

Opting out of specific rules

new FormattingTest()
    .useAll()
    .dontUse(ruleName) // e.g. ruleName = 'exportHasSameNameAsModule'
    .exec();

Rules

  • dotConstructorIsNotUsed: Ensures that "this.constructor" is not found anywhere in application or test files.
  • exportHasSameNameAsModule: Validates (for application files only) the export name. Exactly one of the following must be true: (1) The export name is the same as the file name (not including .js extension), or (2) The export name is the same as the containing folder name, and the file name is index.js.
  • importsDoNotEndWithExtension: Ensures that imports (require()) do not use file extensions. Use "foo" or "./bar/baz" instead of "foo.js" or "./bar/baz".
  • importsDoNotUseIndexIdentifier: Ensures that imports (require()) do not use /index in the oath. Use ./bar/baz instead of ./bar/baz/index.
  • oneClassExportedPerFile: Ensures that there is exactly one export (class or function) per file.