Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Update `check` to include all project specifiers when calling TypeScript Because TypeScript automatically finds all dependencies, this doesn't have any impact on TypeScript's diagnostics * Update `check` to include diagnostics with ESLint * Tweak runtime package to use esbuild using a build script * Update ESLint to use TypeScript parser To use the TypeScript ESLint parser, the ESBuild build script needed to be updated to shim multiple NodeJS APIs * Switch to using `eslint` package directly instead of `eslint-linter-browserify` * Use TypeScript parser when using ESLint in LSP diagnostics * Fix column offsets in LSP for ESLint rules * Move ESLint config to a common module * Reduce "no-unused-vars" rule to a warning * Update LSP and `brioche check` to use ESLint diagnostic levels * Switch to custom `path` NodeJS compatibility module implementation * Fix more errors in `brioche check` * Set up `@typescript-eslint/plugin` * Enable a bunch of ESLint rules from `@typescript-eslint` * Set esbuild script log level to "info" * Enable and tweak some ESLint rules * Switch to `esbuild-plugin-alias-path` The repo for `esbuild-plugin-alias` no longer exists, so it seems like it's no longer supported. `esbuild-plugin-alias-path` also seems to work and produced no actual build changes! * Use `node --loader=ts-node/esm` instead `ts-node-esm` * Enable some optimizations in debug builds This fixes a stack overflow when running tests that was apparently introduced with the new linting rules. It seems to overflow when parsing JS code (somewhere in `swc`) * Update "check" tests to fix errors from new lint rules * Add test for some basic lint rules * Update "check" tests to check diagnostic levels
- Loading branch information