Hi Hacker News — I’m releasing *Essential CDN (E.CDN)* as a beta.<p>Most developer CDNs stop at JavaScript. E.CDN is meant to be a simple, versioned “app-store CDN” for *more than JS*, including:<p>* *JS libraries* (e.g., jQuery versions side-by-side)
* *Scripts that can run in the terminal from a site without downloads.*<p>Everything is served with predictable, versioned paths so you can pin exactly what you want.<p>I also built *Essential Jaws (ejaws)*: a tiny runner that lets you stream a script from the web and execute it immediately from one terminal session (no saving an installer script to disk first).<p>*Examples*<p>JS Libs:<p>```html
<script src="https://essentialcdn.fluidity.workers.dev/jquery/3.7.1/jquery.min.js"></script>
<script src="https://essentialcdn.fluidity.workers.dev/jquery/4.0.0/jquery.min.js"></script>
```<p>Essential Jaws 1:<p>```powershell
# Windows (recommended): stream and run ejaws
iwr -useb <a href="https://essentialcdn.fluidity.workers.dev/ejaws/1.0.0/ejaws.ps1" rel="nofollow">https://essentialcdn.fluidity.workers.dev/ejaws/1.0.0/ejaws....</a> | iex
```<p>Repo / docs:<p>```text
<a href="https://gitlab.com/kryptonitewing/essential.cdn" rel="nofollow">https://gitlab.com/kryptonitewing/essential.cdn</a>
```<p>It’s beta, so I’d love feedback on: URL conventions, what packages/tools to add next, and what would make you trust a “stream-to-run” workflow more (checksums, signatures, pinned tags, etc.).