build: TS6 + oxc.rs

[erickzhao]

This PR migrates us to oxc.rs from ESLint/Prettier. Going to do this across all Ecosystem WG-owned repos.

Migration guidelines

Formatting

• Existing Prettier configuration ported to oxfmt to minimize diff.
• Markdown and YAML ignored.

Linting

• oxlint configuration intentionally kept minimal. All default plugins enabled, with import added as well.
• TypeScript repos attempt to use typeAware mode via oxlint-tsgolint.
  • This is sometimes impossible in a straight migration due to legacy moduleResolution: node settings. This is noted whenever relevant.

Other

• husky + lint-staged set up for pre-commit hooks.
• package.json scripts standardized as lint and lint:fix.
• typescript dependency upgraded to v6 for building the repos. We maintain configuration compatibility with tsgo while keeping a stable version of TypeScript.
  • Where relevant (for packages.electronjs.org repos) typedoc is upgraded to 0.28 accordingly, but this triggers some socket.dev warnings that I would like reviewers to mark as acceptable risk.

Full list of PRs

• build: oxc.rs apps#2202
• build: TS6 + oxc.rs #437
• electron/circleci-secret-service#59
• build: TS6 + oxc.rs devtron#345
• build: TS6 + oxc.rs docs-parser#189
• build: TS6 + oxc.rs fiddle-core#197
• electron/fiddle.electronjs.org#18
• build: TS6 + oxc.rs fuses#106
• build: TS6 + oxc.rs get#388
• build: TS6 + oxc.rs github-app-auth#56
• build: TS6 + oxc.rs llm#58
• build: oxc.rs node-abi#280
• build: oxc.rs node-minidump#149
• build: TS6 + oxc.rs notarize#287
• build: TS6 + oxc.rs osx-sign#420
• build: TS6 + oxc.rs packager#1905
• build: TS6 + oxc.rs rebuild#1261
• build: TS6 + oxc.rs release-status#240
• build: oxc.rs symbolicate-mac#108
• build: TS6 + oxc.rs typescript-definitions#341
• build: TS6 + oxc.rs universal#195
• build: TS6 + oxc.rs update-electron-app#226
• build: TS6 + oxc.rs update.electronjs.org#231
• build: TS6 + oxc.rs windows-sign#104

TODO:

• electron/github-app-auth-action
• electron/remote
• electron/windows-installer

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	oxfmt@​0.44.0
	typescript@​5.5.4 ⏵ 6.0.2	+1		+1
	oxlint@​1.59.0
	typedoc@​0.25.13 ⏵ 0.28.18				-1
	oxlint-tsgolint@​0.20.0

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/typedoc@0.28.18 → npm/entities@4.5.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Obfuscated code: npm markdown-it is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/typedoc@0.28.18 → npm/markdown-it@14.1.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/markdown-it@14.1.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report