Draft spec text #10
Merged
Draft spec text #10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
styfle
reviewed
Jul 28, 2025
| @@ -12,7 +12,7 @@ contributors: Steven | |||
| <h1>Proposal Import Bytes</h1> | |||
| <p>See <a href="https://github.com/styfle/proposal-import-bytes/blob/main/README.md">the explainer</a> for information.</p> | |||
| <emu-note type="editor"> | |||
| <p>This proposal is buit on top of the <a href="https://github.com/tc39/proposal-import-attributes">Import Attributes</a> proposal.</p> | |||
| <p>This proposal is buit on top of the <a href="https://github.com/tc39/proposal-json-modules">JSON Modules</a> and <a href="https://github.com/tc39/proposal-immutable-arraybuffer">Immutable Array Buffer</a> proposals.</p> | |||
There was a problem hiding this comment.
Might need to update the readme as well if we want to swap import-attributes for json-modules
There was a problem hiding this comment.
Actually, I think import-attributes is correct.
This proposal is built on top of import-attributes, not json-modules.
There was a problem hiding this comment.
The way I framed it we are sharing JSON modules text per the next comment.
styfle
reviewed
Jul 28, 2025
| @@ -67,11 +71,11 @@ contributors: Steven | |||
| <p>The actual process performed is host-defined, but typically consists of performing whatever I/O operations are necessary to load the appropriate Module Record. Multiple different (_referrer_, _moduleRequest_.[[Specifer]], _moduleRequest_.[[Attributes]]) triples may map to the same Module Record instance. The actual mapping semantics is host-defined but typically a normalization process is applied to _specifier_ as part of the mapping process. A typical normalization process would include actions such as expansion of relative and abbreviated path specifiers.</p> | |||
|
|
|||
| <emu-note> | |||
| <p><ins>The above text implies that hosts *must* support JSON modules imported with `type: "json"` (if it completes normally), but it doesn't prohibit hosts from supporting JSON modules imported with no type specified. Some environments (for example, web browsers) plan to require `with { type: "json" }`, and environments which want to restrict themselves to a compatible subset would do so as well.</ins></p> | |||
| <p>The above text implies that hosts *must* support JSON modules <ins>and buffer modules</ins> imported with `type: "json"` <ins>and `type: "buffer"` respectively </ins>(if it completes normally), but it doesn't prohibit hosts from supporting JSON modules imported with no type specified. Some environments (for example, web browsers) plan to require `with { type: "json" }`, and environments which want to restrict themselves to a compatible subset would do so as well.</p> | |||
There was a problem hiding this comment.
I think we need to remove the type: "json" part mentioned here, right?
There was a problem hiding this comment.
Because I've based this to JSON modules, it's sharing this note with JSON modules.
|
The rendered spec for this PR is available at https://styfle.github.io/proposal-import-buffer/pr/10. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Threw together some very simple draft spec text, which should be enough for a Stage 2 if there is interest.