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

eslint-plugin-fullfilename

v1.0.2

Published

eslint plugin to verrify that file full path matches naming conventions

Downloads

3

Readme

eslint-plugin-fullfilename

Eslint plugin that allow to verrify that all the files full path match a naming convention.

How to use

  $ npm install eslint-plugin-fullfilename --save-dev

OR

  $ yarn add -D eslint-plugin-fullfilename

Then in .eslintrc

"plugins": [
    "fullfilename"
  ],
  "rules": {
    "fullfilename/match-regex": [2, [
      {"regexp": "SOME_REGEXP"}
    ]]
  }

Documentation

  • The rules are evaluated from top to bottom. Once one of the rule is matched no other rule is checked.

  • To be considered a problem, a file name must not match any regexp or match one that uses failOnMatch see exemples

  • All regexps are validated against the full path from the root of the file system.
    ie: /users/me/my-code/my-project/src/myFile.js

  • Only files that are validated be eslint are checked

Exemples

Multiple rules

"plugins": [
    "fullfilename"
  ],
  "rules": {
    "fullfilename/match-regex": [2, [
      {"regexp": "SOME_REGEXP"},
      {"regexp": "SOME_OTHER_REGEXP"}
    ]]
 }

Fail on match

You can instruct the plugin to treat a match as an error

"plugins": [
   "fullfilename"
 ],
 "rules": {
   "fullfilename/match-regex": [2, [
     {
       "regexp": "SOME_REGEXP",
       "failOnMatch": true
     },
   ]]
}

You can also specify an error message when using failOnMatch

"plugins": [
   "fullfilename"
 ],
 "rules": {
   "fullfilename/match-regex": [2, [
     {
       "regexp": "SOME_REGEXP",
       "failOnMatch": true,
       "message": "the file {{name}} does not respect the rules"
     },
   ]]
}