Usage

Path layout, caching and the few rules there are.

Path layout

https://static-assets-eu.lol/npm/<package>/<version>/<file>

Versions are exact. There is no latest alias on purpose, silent upgrades break things.

Pinning an edge

The apex answers from whichever edge is closest. During a benchmark you may want a fixed one:

https://cdn-a3f81.static-assets-eu.lol/npm/htmx/1.9.12/htmx.min.js
https://cdn-b7d24.static-assets-eu.lol/npm/htmx/1.9.12/htmx.min.js
https://cdn-c5e96.static-assets-eu.lol/npm/htmx/1.9.12/htmx.min.js

Edge names change when hardware is replaced. Do not hardcode them in production.

Caching

• Immutable paths are served with Cache-Control: public, max-age=31536000, immutable
• Directory listings are disabled
• Range requests are supported
• Both HTTP/2 and HTTP/1.1 are served, HTTP/3 is not enabled

Rules

• No hotlinking of anything that is not in the mirrored list
• No use as a general file host, this is not storage
• Fair use on bandwidth, sustained abuse gets the source rate limited

Requesting a package

Send the package name, the version and the license. Small, stable, permissively licensed libraries get added, everything else is declined without much discussion.