Hi Hacker News — I’m releasing *Essential CDN (E.CDN)* as a beta.
Most developer CDNs stop at JavaScript. E.CDN is meant to be a simple, versioned “app-store CDN” for *more than JS*, including:
* *JS libraries* (e.g., jQuery versions side-by-side)
* *Scripts that can run in the terminal from a site without downloads.*
Everything is served with predictable, versioned paths so you can pin exactly what you want.
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).
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.).
telui•1h ago
Most developer CDNs stop at JavaScript. E.CDN is meant to be a simple, versioned “app-store CDN” for *more than JS*, including:
* *JS libraries* (e.g., jQuery versions side-by-side) * *Scripts that can run in the terminal from a site without downloads.*
Everything is served with predictable, versioned paths so you can pin exactly what you want.
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).
*Examples*
JS Libs:
```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> ```
Essential Jaws 1:
```powershell # Windows (recommended): stream and run ejaws iwr -useb https://essentialcdn.fluidity.workers.dev/ejaws/1.0.0/ejaws.... | iex ```
Repo / docs:
```text https://gitlab.com/kryptonitewing/essential.cdn ```
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.).