Post

daniel r(ooooooh) at jsconf mx 🇲🇽
@danielroe.dev

wouldn't it be nice if sites could share a cache of common js? ... stuff like react, or vue or svelte? 👉 there's an early stage proposal for cross-origin storage which enables exactly this. there are challenges but I think it's very interesting indeed

github.comGitHub - WICG/cross-origin-storage: Explainer for the Cross-Origin Storage (COS) APIExplainer for the Cross-Origin Storage (COS) API. Contribute to WICG/cross-origin-storage development by creating an account on GitHub.
Ben Schwarz
@benschwarz.bsky.social

I recall seeing several proposals about popular library caches in the past decade. The general consensus was that it wasn’t worth it, and people didn’t want “blessed” libraries to gain an advantage that could hinder web progress. Is this proposal different in some way?

Thomas Steiner
@tomayac.com

It's different in that it's hash-based, so we don't need to agree on the same CDNs (as when before the caches were isolated by origin). This means the cache hit rates would improve, as we work directly with fullstack frameworks like Nuxt, so they can consider COS at build time.

0 reposts2 likes

Thomas Steiner
@tomayac.com

We propose the Public Hash List (github.com/WICG/cross-o...) as an agreed-on list of shareable resources, based on neutral inclusion criteria without gatekeeping.

github.comPublic Hash List as a way to solve the availability gating challenge · Issue #64 · WICG/cross-origin-storageThe explainer suggests vendors apply availability gating to decide whether a resource can be shared via the COS cache. The repo tomayac/public-hash-list contains some early explorations in the dire...