Skip to content

Why not a phase? #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
styfle merged 1 commit into from
Aug 20, 2025
Merged

Why not a phase? #19

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,6 +163,15 @@ ReadableStream is part of the WHATWG [Streams](https://streams.spec.whatwg.org),

See discussion in Issue https://github.com/styfle/proposal-import-bytes/issues/3

### Why not a phase?

This proposal does not attempt to introduce a new phase like the [source](https://github.com/tc39/proposal-source-phase-imports) or [asset](https://github.com/tc39/proposal-asset-references) proposals.

* A new phase would require a syntax change to JavaScript
* A new phase would cause `Sec-Fetch-Dest` to be script instead of empty

See discussion in Issue https://github.com/tc39/proposal-import-bytes/issues/16

### Why `type: bytes`?

The `bytes()` method is familiar to those using [Response.bytes()](https://developer.mozilla.org/en-US/docs/Web/API/Response/bytes) or newer [Blob.bytes()](https://developer.mozilla.org/en-US/docs/Web/API/Blob/bytes) which both return Uint8Array.