@akcentacz/eslint-config v2.0.0

eslint-config

How to use eslint-config package

• Install the package: npm install @akcentacz/eslint-config --save-dev
• Use the config in your .eslintrc file:

extends: [
  '@akcentacz/eslint-config',
  ...
],

In project, where you want to use the package. You will have to install all the necessary dev dependencies on the level of your project. The reason is that this package doesn't ship dependecies into your project. Feel free and use this command if you want:

npm install eslint-config-prettier eslint-plugin-import eslint-plugin-jest eslint-plugin-jsx-a11y eslint-plugin-react eslint-plugin-react-hooks --save-dev

• If you will be add some dependencies you should rewrite script above and add dependencies into it.
• You can try it in your repository, if you try run build, if you get error Definition for rule *dep-name* was not found, you have to install into your project.

List of dependencies:

• eslint-config-prettier
• eslint-plugin-import
• eslint-plugin-jest
• eslint-plugin-jsx-a11y
• eslint-plugin-react
• eslint-plugin-react-hooks

How to publish new version with semantic version

Any changes goes with semantic versioning, more info at Keep a Changelog and Semantic Versioning

By default, scoped packages are published with private visibility.

1. To change the version number in package.json, on the command line, in the package root directory, run the following command, replacing <update_type> with one of the semantic versioning release types (patch, major, or minor): npm version <update_type>

2. Run: npm adduser, then npm publish

3. To see your private package page, visit https://npmjs.com/package/*package-name

Private packages will say private below the package name on the npm website.