ESLint Configuration
ESLint statically analyzes your code to quickly find problems. It is built into most text editors and you can run ESLint as part of your continuous integration pipeline. - https://eslint.org/
This is the shared eslint configuration used at My Company
for code formatting.
Usage
Install the package
npm install --save-dev @golms/eslint-config
Add the configuration
Create or update the .eslintrc.js
file in your projects root directory accordingly.
module.exports = {
extends: ["@golms/eslint-config"],
};
Extend or Override configuration
This is not recommended as the goal is to have similar settings in all projects, but if for some reason you need to add or change the configuration, it is possible in the following way.
Run
npx prettier --write .
Options
Opinionated Options that differ from the standard/recommended eslint configurations.
*import/order*
: Enforce a alphabetical sorting convention in the order of require()
/ import
statements.
Local Development
Install Dependencies
npm install
Test
npm test
Repair
This command may be useful when obscure errors or issues are encountered. It removes and recreates dependencies of your project.
npm run repair
Release
Fully automated version management and package publishing via semantic-release. It bumps the version according to conventional commits, publishes the package to npm and release a new version to GitHub.
Automatic Release (GitHub Action) [Recommended]
Make sure that the secrets GITHUB_TOKEN
and NPM_TOKEN
are available in GitHub repository.
npm run release:ci
Manual Release
Make sure that the environment variables GITHUB_TOKEN
and NPM_TOKEN
are set or declared in .env
and a productive build was previously created via npm run build
.
npm run release
Show your support
Give a ⭐️ if this project helped you!
License
Copyright © 2022 Boehringer Ingelheim.
This project is MIT licensed.
Resources