Describe the bug
When a module contains some specific tagged templates, and it loaded in dev via runner.import, the OXC runtime comes into play and some tags are escaped, probably for safety.
While this might be the correct behaviour, it isn't documented the migration guide, and it can't be turned off.
This breaks Astro rendering, where we sometime render <script> tags.
Reproduction
https://github.com/ematipico/test-errors/tree/bug/oxc-runtime
Steps to reproduce
- Checkout the repository
- Checkout the branch
bug/oxc-runtime
- Run
node repro-oxc-runtime.mjs
I spawned an agent which dumped its discoveries in a markdown file
System Info
System:
OS: macOS 26.3.1
CPU: (12) arm64 Apple M4 Pro
Memory: 12.99 GB / 48.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 24.12.0
npm: 11.6.2
pnpm: 10.28.0
Browsers:
Chrome: 145.0.7632.160
Firefox: 146.0.1
Safari: 26.3.1
npmPackages:
vite: ^8.0.0-beta.13 => 8.0.0-beta.18
Used Package Manager
pnpm
Logs
No response
Validations
Describe the bug
When a module contains some specific tagged templates, and it loaded in dev via
runner.import, the OXC runtime comes into play and some tags are escaped, probably for safety.While this might be the correct behaviour, it isn't documented the migration guide, and it can't be turned off.
This breaks Astro rendering, where we sometime render
<script>tags.Reproduction
https://github.com/ematipico/test-errors/tree/bug/oxc-runtime
Steps to reproduce
bug/oxc-runtimenode repro-oxc-runtime.mjsI spawned an agent which dumped its discoveries in a markdown file
System Info
System: OS: macOS 26.3.1 CPU: (12) arm64 Apple M4 Pro Memory: 12.99 GB / 48.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 24.12.0 npm: 11.6.2 pnpm: 10.28.0 Browsers: Chrome: 145.0.7632.160 Firefox: 146.0.1 Safari: 26.3.1 npmPackages: vite: ^8.0.0-beta.13 => 8.0.0-beta.18Used Package Manager
pnpm
Logs
No response
Validations