PR Checklist

The Angular transform filter matched query-stringed ids like foo.ts?raw via TS_EXT_REGEX
(/\.[cm]?ts(?[a-z])/, which is not anchored and ignores the query string). The id entered the
handler, the query was stripped, and Angular/esbuild recompiled the file as TypeScript — discarding
the export default "<source>" that Vite's native raw loader had already produced. As a result
import src from './file.ts?raw' failed with "default" is not exported by "….ts?raw". This broke
the documented Vite ?raw import for every .ts/.cts/.mts file (Angular component or plain
TypeScript alike), e.g. feeding a story component's source into a Storybook "Show code" panel.

Closes #2356

Affected scope

• Primary scope: vite-plugin-angular
• Secondary scopes: none

Recommended merge strategy for maintainer [optional]

• Squash merge
• Rebase merge
• Other

What is the new behavior?

?raw-queried ids are now added to the transform.filter.id.exclude array in both the AOT
(angular-vite-plugin.ts) and fast-compile (fast-compile-plugin.ts) plugins, so the Angular
transform never runs for them and Vite's built-in raw handling stands:

exclude: [/node_modules/, 'type=script', '@ng/component', /[?&]raw\b/],

/[?&]raw\b/ matches foo.ts?raw and foo.ts?import&raw, but not plain foo.ts nor legitimate
query ids the handler must still compile (HMR foo.ts?t=123, foo.ts?component). The fix is
content-agnostic, so it covers both Angular and non-Angular .ts files.

// now works as with stock Vite
import source from './my-component.ts?raw';
console.log(source); // the file contents as a string

Test plan

• nx format:check
• pnpm test (vite-plugin-angular — new exclusion specs in angular-vite-plugin.spec.ts and
  fast-compile-plugin.spec.ts assert ?raw ids are excluded while plain/HMR ids still compile)
• Manual verification

Does this PR introduce a breaking change?

• Yes
• No

Other information

The plugin already routed .html?raw through a virtual id, but that mechanism exists solely to
satisfy Vite's server.fs Denied-ID security check — .html never reaches the Angular transform.
The .ts?raw problem is purely the transform filter shadowing Vite's raw output, so the narrow
filter-exclusion fix is the right tool and leaves the .html?raw path untouched.

Generated by Claude Code