refactor(deps): gazelle migration — enable automatic dep management for all packages

[longlho]

Summary

Complete gazelle migration: decompose all custom macros, create gazelle-compatible formatjs_ts_project wrapper, and enable gazelle JS for automatic srcs and deps management across 31 of 32 packages.

Phase 3: Decompose vitest macro

• Created vitest_runner in tools/vitest.bzl (test runner + snapshots, no type-checking)
• Exported TEST_TSCONFIG, VITEST_DEPS, VITEST_DOM_DEPS

Phase 4: Enable gazelle with map_kind

• Created formatjs_ts_project macro in tools/formatjs_lib.bzl:
  • Library mode: typecheck ts_project (tsgo) + transpile ts_project (oxc) + js_library
  • Test mode: typecheck ts_project + vitest_runner
• Root directives: map_kind ts_project formatjs_ts_project, naming conventions, file patterns
• Removed manual ts_project + js_library + vitest_runner from gazelle-managed packages

Fix ESNEXT tsconfig mismatch

• Added "target": "ESNext" to 6 package tsconfig.json files so auto-generated _typecheck_test targets pass

Move scripts/ to own Bazel packages

• Created BUILD.bazel in 14 scripts/ directories + ts-transformer/tests/fixtures/
• Establishes package boundaries so gazelle doesn't glob codegen scripts into lib srcs
• Enabled gazelle for all polyfill packages

Result

Status	Count	Packages
Gazelle-managed	31	All packages except editor
Disabled	1	editor (WIP/commented-out code)

bazel run //:gazelle now automatically manages srcs and deps for library and test targets by reading TypeScript imports.

Test plan

• All tests pass (37 pass, 1 pre-existing flaky failure)
• Zero build failures
• Gazelle converges: 74 BUILD files visited, 0 updated
• All lefthook hooks pass
• CI passes

🤖 Generated with Claude Code

[graphite-app]

Duplicate test target detected. The formatjs_ts_project(name="unit_test", testonly=True) on line 50 will create a vitest_runner target named "unit_test" that runs the same test file vue/integration.test.ts that's already being executed by the vitest_runner(name="vue_integration_test") target on lines 32-48.

When formatjs_ts_project is called with testonly=True, it internally calls vitest_runner (see tools/formatjs_lib.bzl line 161). This means the same test will run twice under different target names, causing:

• Wasted CI time
• Potential confusion about test results
• Maintenance burden

Fix: Remove this duplicate formatjs_ts_project block entirely since the test is already properly configured with the explicit typecheck + runner pattern above:

# Remove lines 50-66 completely

Spotted by Graphite



Is this helpful? React 👍 or 👎 to let us know.

[graphite-app]

The compiler_options values are always quoted as strings, which will produce invalid JSON for boolean/numeric values. For example, {"strict": True} becomes "strict": "True" instead of "strict": true.

# Fix: Handle different value types
if compiler_options:
    opts_parts = []
    for k, v in compiler_options.items():
        if type(v) == "bool":
            val_str = "true" if v else "false"
        elif type(v) == "int":
            val_str = str(v)
        else:
            val_str = '"%s"' % v
        opts_parts.append('    "%s": %s' % (k, val_str))
    opts_lines = ",\n".join(opts_parts)

Suggested change

	opts_lines = ",\n".join([' "%s": "%s"' % (k, v) for k, v in compiler_options.items()])
	content = '// @generated\n{\n // This is purely for IDE, not for compilation\n "extends": "%s",\n "compilerOptions": {\n%s\n }\n}\n' % (extends_path, opts_lines)
	if compiler_options:
	opts_parts = [' "%s": %s' % (k, "true" if v else "false" if type(v) == bool else str(v) if type(v) == int else '"%s"' % v) for k, v in compiler_options.items()]
	opts_lines = ",\n".join(opts_parts)
	else:
	opts_lines = ""
	content = '// @generated\n{\n // This is purely for IDE, not for compilation\n "extends": "%s",\n "compilerOptions": {\n%s\n }\n}\n' % (extends_path, opts_lines)

Spotted by Graphite



Is this helpful? React 👍 or 👎 to let us know.