## Summary
- automatically apply A-codegen to changes under packages/codegen
- keep the Rust and TypeScript code generators in the same functional area
## Naming
Reuse A-codegen because recent packages/codegen PRs already receive it manually. A-printer is stale, while names such as A-codegen-js or P-codegen would introduce a distinction or label prefix the repository does not currently use.
## What
Ports the Relay `graphql` tagged template transform (babel-plugin-relay / swc_relay) as an individual napi transform, per #24914:
- **`crates/oxc_relay`** — the core transform as its own crate (modeled on `oxc_react_compiler`): replaces `graphql` tagged templates with references to relay-compiler artifacts. Definition names are extracted textually like `swc_relay` (equivalent to `\b(fragment|mutation|query|subscription)\s+(\w+)` with `#` comments stripped; hand-rolled scanner, no regex dependency).
- **`napi/transform-relay`** (`oxc-transform-relay`) — standalone napi package copied from the `napi/transform-react` template: parse → semantic → relay traverse → codegen. Only `graphql` tags are rewritten; TypeScript/JSX syntax is preserved untouched, so the output composes with any downstream toolchain.
## Options
| option | default | behavior |
|---|---|---|
| `artifactDirectory` | unset | when set, the import path is computed lexically relative to the transformed file (babel-plugin-relay `getRelativeImportPath` semantics — swc emits absolute paths instead); unset → `./__generated__/` next to the file |
| `language` | `javascript` | `typescript` imports `Name.graphql.ts`, otherwise `Name.graphql.js` |
| `eagerEsModules` | `true` | hoisted default imports (babel-plugin-relay ≥ v17 parity); `false` emits inline `require()` (`@swc/plugin-relay` / Next.js behavior) |
A `graphql` tag with no extractable definition name produces an error diagnostic (babel throws; swc silently skips).
Not supported, documented in both READMEs: dev-mode artifact hash validation, `jsModuleFormat: "haste"`, `isDevVariableName`, swc's Next.js-specific `projects`/`pagesDir`, and GraphQL document validation.
closes#24914
---
Implemented with Claude Code.
This updates the `A-linter-plugins` label rule so changes to the generated oxlint package config no longer trigger the plugin-area label.
The old matcher used `apps/oxlint/src-js/**`, which also caught `apps/oxlint/src-js/package/config.generated.ts`. This splits that coverage into root `src-js` files, non-package subdirectories, and package files except `config.generated.ts`, keeping the rest of the existing plugin/test/conformance coverage intact.
#16650 added conformance tests for Oxlint JS plugins in `apps/oxlint/conformance`. Tag any PRs which alter the contents of this directory with `A-linter-plugins` label.
Add "A-linter" label to PRs which change files in `apps/oxlint`.
Ditto for changes to files in `napi` or `apps` directories.
It was becoming annoying manually adding "A-linter" label to every PR related to Oxlint plugins, which mostly touch files in `apps/oxlint` directory.
Part of #5068, suggested by @ematipico and @MichaReiser, where @leaysgur
and I explored using biome formatter as the base and made a success. All
credits to the old Rome and the new Biome team.
This PR is in a boilerplate state where some of the functions are marked
as `todo!()`.
I also made the following changes:
* changed the base to be less generic, removed the `Language` and
`Context` generics
* expanded the formatter lifetime to include an `'ast` lifetime
* added access to the source text and comments
* added a mechanism for tracking and accessing parent ast nodes (done by
our codegen)
* removed most of the unit tests because they no longer compile
* removed the `oxc_prettier` crate
closes#273closes#814
HIR is removed from this PR, with the minifier being commented out.
HIR is a wonderful idea for compiling to lower languages, but after
sitting on it for a few months I found that it only adds confusion and
uncertainties to both myself and future contributors.
It also adds too much burden to maintainers if we plan to support more
downstream tools.
1 AST is the only way.
camc314