@aladdin-add Can you finish this PR? It's 99% complete, but I'm not 100% confident with ESLint internals.
At least you got your custom rules now.

Need to optimize and tweak the configuration

Linter rules default folder

/scr/linter/rules

Default config rules

kataw:recommended is located here:

/scr/configuration/config

I was writting a cli for kataw in JS(~50%, not pushed yet). but this one seems has a better completeness. :-( 

will look later. :)

the main reason to use JS - dogfooding. :)

It's not a CLI, but loading config file and linter rules. The performance is horrible. It take near 157 ms to load while a simple parser load take 9 ms.
So you need to improve performance and get rid of all try / catch I put in there

Ideal if this could be re-written to use some kind of parallel processing and lazy loading, but I haven't used many of the NodejS I/O methods for years so I'm outdated :)

@aladdin-add friendly ping

seems the code has a few i/o related code; it will block users run it on non-node.js env (e.g. browsers).

what do you think put it in another package(build on the top of kataw core), so we can focus the public API in this one?

The code is to get the config file. Will it not be an issue if we put it in another package to get the linter rules that the compiler needs?

What kind of i/o blockers? It only load a config file, if linting is enabled it grab the rules and return.

This is only for CLI, and that is NodeJS. Not browsers

const config = getconfigFromCli() // the code in this PR

compiler(files, conig);

I'm less active now do to RL and I'm also experimenting with incremental parsing that will be part of the CLI

well, another option is to add an entry "bin" to load the config. But let's do not do io related op in "src/index.ts".

it is the same as eslint doing: https://github.com/eslint/eslint/blob/3b6cd8934b3640ffb6fa49b471babf07f0ad769a/package.json#L6-L9

Ok. Can you remove from "index.ts" and move to a more propriate place and load from binary as in ESLint?

@aladdin-add any progress on this? I managed to get incremental parsing working. Need to add an CLI option for it.