Update JS deps and eslint enhancements

[silverwind]

• Update all JS deps
• Tested affected dependencies
• Replace eslint unstable_native_nodejs_ts_config with optional jiti dependency. This will be more compatible with editor integrations that may not pass this flag.
• Enable @typescript-eslint/array-type and autofix issues
• Enable @typescript-eslint/no-useless-default-assignment and fix 1 issue. disabled again, false positive.
• Enable additional eslint rules, no new issues
• Move typescript to devDependencies because make frontend works without it

[lunny]

It seems string[] looks more better than Array<string> in most situation.

[silverwind]

For simple types maybe but once they get complex, generic form is superior, e.g. Array<Foo | Bar> is more readable than (Foo | Bar)[]. And once you start using generic syntax, you question why there are two syntax variants in use so I just like to default to one syntax. There is a array-simple option too but I find it unsuitable because I don't want to forbid generic syntax for simple types.

It's not a big issue for me, if people prefer the [] (maybe because they come from go), we can continue to allow both syntaxes. I will only be writing generic syntax though.

[wxiaoguang]

It's not a big issue for me, if people prefer the [] (maybe because they come from go), we can continue to allow both syntaxes. I will only be writing generic syntax though.

I also prefer string[] when the type is simple. Not only Go, but also PHP, Java, C/C++, C#, etc

[silverwind]

I guess then we need to disable the lint rule because the option array-simple is too strict as it forces simple types to always use [], while we then would want it to accept both variants for simple types at least.

[silverwind]

BTW here are more arguments why the generic syntax is superior: https://tkdodo.eu/blog/array-types-in-type-script

[silverwind]

Reverted the array type changes and updated dependencies again, should be ready now.