Skip to content

clarify cache key behavior #8

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
merged 1 commit into from
Jul 18, 2025
Merged

clarify cache key behavior #8

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
6 changes: 6 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,6 +81,12 @@ All of the import statements in the module graph that address the same module wi

The determination of whether the `type` attribute is part of the module cache key is left up to hosts (as it is for all import attributes).

For example, `import "foo"` and `import "foo" with { type: "buffer" }` may return the same module in one host, and different modules with another host. Both are valid implementations.

However, a dynamic import and a static import with the same `type` will return the same module, regardless of host.

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

### Is there any prior art?

Deno 2.4 added support in [July 2025](https://deno.com/blog/v2.4) to inline a Uint8Array
Expand Down