https://github.com/wintercounter/eslint-global-patch
From ESLint@6 the possibility was removed to use global configs and plugins. This npm package will patch your ESLint installation to add support back.
https://github.com/wintercounter/eslint-global-patch
Last synced: about 1 year ago
JSON representation
From ESLint@6 the possibility was removed to use global configs and plugins. This npm package will patch your ESLint installation to add support back.
- Host: GitHub
- URL: https://github.com/wintercounter/eslint-global-patch
- Owner: wintercounter
- License: mit
- Created: 2019-10-23T13:21:18.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2021-10-23T10:37:08.000Z (almost 5 years ago)
- Last Synced: 2025-06-19T09:13:42.481Z (about 1 year ago)
- Language: JavaScript
- Homepage:
- Size: 7.81 KB
- Stars: 17
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# eslint-global-patch
From ESLint@6 the possibility got removed to use global configs and
plugins. This npm package will patch you ESLint installation to add
support back.
> THIS IS A HIGHLY DANGEROUS AND UGLY PACKAGE! ONLY USE AT YOUR OWN
> RISK IN CASE THERE IS NO OTHER WAY!
This package will basically do a string-replace on your eslint
installation. When it'll try to resolve a plugin/config relative to
your source file and if it fails, it will try to find them also relative
to the patched file: `eslint/lib/shared/relative-module-resolver.js`.
This package can stop working with any ESLint update, I'll try to update
it ASAP. For now the versioning strategy is to use the same ESLint version
number where the braking change introduced.
Usage:
```sh
npm i eslint-global-patch
```
The script will patch ESLint on `postinstall` automatically.
## Why not create an issue at ESLint?
https://github.com/eslint/eslint/issues/11914