eslint-plugin-lvmcn
v0.0.5
Published
ESLint plugin for custom rules.
Downloads
14
Readme
eslint-plugin
Usage
Basic setup
To use this plugin, install it as a devDependency
first, alongside ESLint
itself:
npm install --save-dev eslint-plugin-lvmcn eslint
Rules
| Rule | Description | Configurations | Fixable | | -------------------------------- | ------------------------------------------------------ | ---------------- | -------- | | no-single-line-comment-block | Single line comments should not be in a block comment. | | |
Getting Started
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See usage notes on how to consume this package in your project.
Prerequisites
Minimal requirements to set up the project:
- Node.js v14, installation instructions can be found on the official website, a recommended installation option is to use Node Version Manager. It can be installed in a few commands.
- A package manager npm. All instructions in the documentation will follow the npm syntax.
- Optionally a Git client.
Installing
Start by cloning the repository:
git clone [email protected]:tinymins/eslint-plugin-lvmcn.git
In case you don't have a git client, you can get the latest version directly by using this link and extracting the downloaded archive.
Go the the right directory and install dependencies:
cd eslint-plugin-lvmcn
npm install
That's it! You can now go to the next step.
Tests
Formatting
This project uses Prettier to automate formatting. All supported files are being reformatted in a pre-commit hook. You can also use one of the two scripts to validate and optionally fix all of the files:
npm run format
npm run format:fix
Linting
This project uses ESLint to enable static analysis. TypeScript files are linted using a custom configuration. You can use one of the following scripts to validate and optionally fix all of the files:
npm run lint
npm run lint:fix
Coverage
Built with
Runtime libraries
Automation
Source
Delivery
Versioning
This project adheres to Semantic Versioning v2.