Files
camc314 1599f111b6 fix(linter): align lsp extends default plugins (#22788)
Fixes #22758.

The LSP path was not materializing the default plugin set before resolving a root config with `extends`, while the CLI path already did that before building the config. That meant a child config launched as the LSP workspace root could extend a parent config with an explicit `plugins` array and accidentally lose default plugins like `typescript`, even though `oxlint` CLI and `--print-config` showed those plugins as active.

This moves the default-plugin materialization into a shared helper used by both CLI and LSP config loading, so both paths resolve the same effective root config before `extends` are applied.

I added a regression fixture for the reported nested config shape and snapshot coverage for the missing TypeScript diagnostic.
2026-05-28 19:37:30 +00:00
..