Add type: "text" import attribute

[eemeli]

Description

Adds documentation for the upcoming type: 'text' import attribute.

Motivation

I'm the proposal champion, and would like to advance it.

Additional details

The proposal is specified in:

• tc39/proposal-import-text
• Add text imports whatwg/html#11933
• Add "text" destination type, for JavaScript text imports whatwg/fetch#1898
• Add "text" destination type, for JavaScript text imports w3c/webappsec-csp#794

[github-actions]

Preview URLs (3 pages)

• /en-US/docs/Web/API/Request/destination
• /en-US/docs/Web/HTML/Reference/Attributes/rel/modulepreload
• /en-US/docs/Web/JavaScript/Reference/Statements/import/with

External URLs (3)

URL: /en-US/docs/Web/JavaScript/Reference/Statements/import/with
Title: Import attributes

• https://github.com/tc39/proposal-import-text (1 time) (Note! This may be a new URL 👀)
• https://html.spec.whatwg.org/multipage/webappapis.html (1 time) (Note! This may be a new URL 👀)
• https://tc39.es/ecma262/multipage/ecmascript-language-scripts-and-modules.html (1 time) (Note! This may be a new URL 👀)

(comment last updated: 2026-03-23 11:01:03)

[Josh-Cena]

LGTM

[hamishwillee]

@eemeli Is this supported by any browser? I was expecting to see a text key in the browser compatibility section of each of the places you added the addition - such as https://pr43505.review.mdn.allizom.net/en-US/docs/Web/JavaScript/Reference/Statements/import/with#browser_compatibility

This is important because MDN only documents things that are available in browsers (though not necessarily released).

I'm (very) happy with the docs updatd. I've added request changes though, because we shouldn't merge this until the corresponding browser compatibility data has merged. Can you link that in the description?