[Feature]: optimize the ecma version check.

[easy1090]

What problem does this feature solve?

1. Support users in configuring the version number for ECMAScript testing.
2. Support for ecma version 8.

What does the proposed API look like?

linter: {
        rules: {
          'ecma-version-check': [
            'Error',
            {
              checkVersion: 7, // enum, 6 | 7 | 8
              exclude: [] // exclude some files. 
            },
          ],
        },
    }

[nyqykk]

checkVersion maybe better changed to ES2015 and so on

[chenjiahan]

@nyqykk How about align options with rsbuild-plugin-check-syntax:

https://github.com/rspack-contrib/rsbuild-plugin-check-syntax?tab=readme-ov-file#options

[nyqykk]

Good suggestion

@nyqykk How about align options with rsbuild-plugin-check-syntax:

https://github.com/rspack-contrib/rsbuild-plugin-check-syntax?tab=readme-ov-file#options

[nyqykk]

we will add this feature after refactor Overview UI #615

[turnerguo]

I's better to directly use browserslist settings which provided by project, then consider to provide some config options to override it.

[easy1090]

yes, our current plan is like this.

I's better to directly use browserslist settings which provided by project, then consider to provide some config options to override it.

[nyqykk]

support in v1.0 #655

[nanianlisao]

Can it support a specific syntax level? For example, Chrome 70? Through syntax checking, of course, this may be a hard job, and I haven’t seen any actual cases to do this. This is more intuitive and more useful

[nyqykk]

Can it support a specific syntax level? For example, Chrome 70? Through syntax checking, of course, this may be a hard job, and I haven’t seen any actual cases to do this. This is more intuitive and more useful

ofcource it supports that，like this https://github.com/rspack-contrib/rsbuild-plugin-check-syntax?tab=readme-ov-file#options

[nanianlisao]

Great feature!

Can you list all the problems? For example, if I target chrome 70, can you list all the syntax checks that exceed chrome 70 to form a list. This will make it easier for me to modify it. Instead of just handling one and throwing an exception to terminate the whole process

In fact, most of the syntax outside the target is caused by skipping swc transform, such as npm package code under node_modules. I hope to be able to use this method to check and set the appropriate target and include. This is what rsdoctor can provide

[nyqykk]

It will list all files exceed syntax check but just throw the first error in each file even if it has multiple errors. Only by solving the first problem can the second problem be scanned