Skip to content

Commit 5af33b8

Browse files
authored
clarify cache key behavior (#8)
- Closes #4
1 parent 49e313e commit 5af33b8

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,12 @@ All of the import statements in the module graph that address the same module wi
8181

8282
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).
8383

84+
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.
85+
86+
However, a dynamic import and a static import with the same `type` will return the same module, regardless of host.
87+
88+
See discussion in Issue https://github.com/styfle/proposal-import-bytes/issues/4
89+
8490
### Is there any prior art?
8591

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

0 commit comments

Comments
 (0)