Drop `es/lints` except critical lints

[kdy1]

We cannot replace eslint because of plugins and the conclusion of the discussion was to drop it

[ArturAralin]

Maybe I'll make own repo with non critical lints based on swc crate

[alexander-akait]

I think time to create swc_linters (i.e. swc_ecma_lint/swc_css_lint and maybe swc_html_lint in future), so it will be more scalable and will not distract the main swc repo and team (in future).

In long term I think we should replace eslint/stylelint, our parser and AST are great, perf is better, it will happen sooner or later anyway

[kdy1]

I'll not remove rules from the repository, I'll just move it to @swc/lints

I'll review your PRs soon

[Austaras]

Is swc cureently bundling its own wasm runtime? Does that mean after seperation user need to keep two identical wasm runtime on disk?

[kdy1]

No we don't bundle wasm

[IWANABETHATGUY]

Any plan to support code fix/code suggestion like eslint?

[ArturAralin]

@IWANABETHATGUY lints will not have any formatting checks

#3888 (comment)

[IWANABETHATGUY]

@IWANABETHATGUY lints will not have any formatting checks

#3888 (comment)

Nope, code fix not equals to formatting checks.

[IWANABETHATGUY]

@IWANABETHATGUY lints will not have any formatting checks

#3888 (comment)

But thanks for explaining.

[IWANABETHATGUY]

I mean something like this.

[Austaras]

No we don't bundle wasm

Would #5350 result in final binary?

[kdy1]

No, but we may replace native bindings for some platforms with wasm runtime.
Until stabilizing it, we will bundle wasm runtime (@swc/wasm) for those platforms.

(Note: We bundle wasmer, which is also a wasm runtime. So we may need to distinguish them)

[kdy1]

Oh, if you mean wasmer (for wasm runtime), the linter does not use wasm runtime at the moment.