5 Commits (1c7339e385764f4e53be0cbda5043d2915b49277)

Author	SHA1	Message	Date
silverwind	c8ea41b049	Fix remaining typescript issues, enable `tsc` (#32840) ... Fixes 79 typescript errors. Discovered at least two bugs in `notifications.ts`, and I'm pretty sure this feature was at least partially broken and may still be, I don't really know how to test it. After this, only like ~10 typescript errors remain in the codebase but those are harder to solve. --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>	2 months ago
silverwind	d061f6b70a	Change typescript `module` to `nodenext` (#32757) ... Typescript 5.7 changed semantics around JSON imports and `nodenext` is now [treated differently](https://devblogs.microsoft.com/typescript/announcing-typescript-5-7-beta/#validated-json-imports-in---module-nodenext) than `node16` for JSON imports and it requires the import attribute, so change the value to that and add the attribute to eliminate this typescript error. [`moduleResolution`](https://www.typescriptlang.org/tsconfig/#moduleResolution) is treated as an alias when `module` is `nodenext`, so we don't need to specify it. Also see https://github.com/microsoft/TypeScript/issues/60589. It appears the next Typescript release will fix this for `node16`, but I guess it'll still be good to switch to `nodenext`.	3 months ago
silverwind	e5e40787dc	Move web globals to `web_src/js/globals.d.ts` (#31943) ... This file serves exclusively to support `web_src/js`, so move it there.	6 months ago
silverwind	5791a73e75	Convert frontend code to typescript (#31559) ... None of the frontend js/ts files was touched besides these two commands (edit: no longer true, I touched one file in 61105d0618 because of a deprecation that was not showing before the rename). `tsc` currently reports 778 errors, so I have disabled it in CI as planned. Everything appears to work fine.	8 months ago
silverwind	08579d6cbb	Add initial typescript config and use it for eslint,vitest,playwright (#31186) ... This enables eslint to use the typescript parser and resolver which brings some benefits that eslint rules now have type information available and a tsconfig.json is required for the upcoming typescript migration as well. Notable changes done: - Add typescript parser and resolver - Move the vue-specific config into the root file - Enable `vue-scoped-css/enforce-style-type` rule, there was only one violation and I added a inline disable there. - Fix new lint errors that were detected because of the parser change - Update `i/no-unresolved` to remove now-unnecessary workaround for the resolver - Disable `i/no-named-as-default` as it seems to raise bogus issues in the webpack config - Change vitest config to typescript - Change playwright config to typescript - Add `eslint-plugin-playwright` and fix issues - Add `tsc` linting to `make lint-js`	8 months ago