Automatically generate your stand-alone dependency free `typescript-eslint` custom config. All the rules you need are intelligently imported from the most popular configs like airbnb. All clashes with prettier are removed.
Automatically create your own custom .eslintrc.json
config file containing rules taken from eslint-config-airbnb-typescript
with the following modifications:
off
rules removed as they are not needed as overridesimport
plugin used by the airbnb rules removed to allow the creation of one dependency free config fileeslint-config-prettier
typescript-eslint/recommended
___
.-' `'.
/ \
| ;
| | ___.--,
_.._ |0) ~ (0) | _.---'`__.-( (_. airbnb rules
__.--'`_.. '.__.\ '--. \_.-' ,.--'` `""`
( ,.--'` ',__ /./; ;, '.__.'` __
_`) ) .---.__.' / | |\ \__..--"" """--.,_
`---' .'.''-._.-'`_./ /\ '. \ _.-~~~````~~~-._`-.__.'custom rules
| | .' _.-' | | \ \ '. `~---`
\ \/ .' \ \ '. '-._)
\/ / \ \ `=.__`~-.
/ /\ `) ) / / `"".`\
, _.-'.'\ \ / / ( ( / /
`--~` ) ) .-'.' '.'. | (
(/` ( (` ) ) '-; bloat! spit it out...
` '-; (-'
Right now he only cares about using typescript-eslint
for TypeScript linting (sensible creature), but I might pursuade him to munch on plain JavaScript files too.
He only comes to life if deno
is installed, he is fanatical about using only the best and latest technology.
deno run --allow-read --allow-write --allow-run mod.ts
or:
mod.ts
executable and start with ./mod.ts