This PR adds support for the import bytes (stage 2.7) and import text (stage 3) proposals:

import logo from "./logo.png" with { type: "bytes" }; // Uint8Array
import readme from "./README.md" with { type: "text" }; // string

const { default: logo } = await import("./logo.png", { with: { type: "bytes" } });

As in the proposals, the file type is ignored: any file can be imported as either bytes or text.

Implementation

Rollup and rolldown both parse the syntax, but neither implements the semantics, and rolldown drops import attributes entirely before they reach plugins (resolveId only receives { isEntry, kind }). An attribute-driven resolveId would therefore only ever work on the rollup path.

Instead, a new nitro:import-attributes plugin pre-transforms the syntax into the existing raw import machinery, which gives a single code path for rollup, rolldown and vite, in both dev and prod:

• import b from "./f.bin" with { type: "bytes" } → import b from "bytes:./f.bin"
• import("./f.bin", { with: { type: "bytes" } }) → import("bytes:./f.bin"), so the namespace default is the Uint8Array as specified
• export ... from ... with { type: "..." } is handled by the same path

Parsing (oxc) and sourcemaps (MagicString) come from rolldown, already a direct dependency, so no new dependencies are added. Modules are only parsed when the attribute is actually present.

The raw plugin gains bytes: and text: prefixes next to the existing raw: one: raw: infers from the file mime, while bytes:/text: always yield a Uint8Array/string (required, as the attributes ignore the file type).

Bug fix

Resolved raw ids now carry a .js suffix. Without it, plugins matching the original extension claim the virtual module after the raw plugin has already turned it into JS: both @rollup/plugin-json (id.slice(-5) === ".json") and vite's json plugin (/\.(json|json5)($|\?)/) then fail with Could not parse JSON file. This also affected the existing raw: prefix for .json files.

Tests

Regression tests in the main fixture (/import-attributes), running against all presets:

• static bytes import of a 256 byte file containing every byte value (verifies the base64 round trip exactly)
• .sql imported as bytes and .json imported as text (the type-ignored cases)
• the same .txt file dynamically imported as both bytes and text

Verified against the rollup, rolldown and vite builders, dev, and the cloudflare preset.

Notes

TypeScript implements neither proposal and types these imports by file extension, so user code still needs // @ts-ignore or a cast. This is noted in the docs.

🤖 Generated with Claude Code