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

fnlint

v1.5.1

Published

File name format linter

Downloads

51

Readme

fnlint

Lint file name formatting.

CircleCI branch Coveralls branch npm

Installation

With npm:

npm i fnlint --save

With yarn:

yarn add fnlint

Usage

Command Line

Create a config file (an object exporting .js file or .json) with your fnlint configuration. See Options below. Then call fnlint referencing the config file:

fnlint --config fnlint.json

Module

fnlint(options: {}, callback: Function(error: Error, results: {})) => Void

  • run linter on given options
  • callback is called once linting completes

fnlint.sync(options: {}) => results: {}

  • synchronous version

fnlint.promise(options: {}) => Promise(results: {})

  • promise version

Results

  • ok Boolean pass value. true if all files pass.
  • passing Array of passing file paths.
  • failing Array of failing file paths.

Example

fnlint({
  basePath: './lib',
  files: '**/*.js',
  format: 'kebabcase'
}, (err, results) => {
  assert.ifError(err);
  if (!results.ok) {
    process.exit(1);
  }
});

Options

  • basePath Base path for files to lint.
  • files Glob string for files to lint relative to base path.
  • format File name format.
  • reporter (optional) Set to false to turn off console reporter.
  • directories (optional) Set to true to lint full path including directories.

Available Formats

  • kebabcase (e.g. kebab-case.js)
  • camelcase (e.g. camelCase.js)
  • pascalcase (e.g. PascalCase.js)
  • snakecase (e.g. snake_case.rb)

Contributing

Don't be shy! Submit issues (or better yet PRs) if you see anything that could be better. If you're submitting code that contains patches or features please try to include unit tests. Thanks!

Commit Messages

Please use the angular changelog convention for your commit messages.

License

MIT : http://opensource.org/licenses/MIT

TODO

  • [ ] Custom file path parsers
  • [ ] Custom matchers
  • [x] CLI