DEPLOYLANE STATIC / REFERENCE
MANIFEST.
BYTE FOR BYTE.
The repository contains two bundled example releases. Each has an HTML entry point, a CSS file and a JavaScript file. The browser calculates metadata from those actual example contents.
[ OPEN REPOSITORY ↗ ] · [ GETTING STARTED ] · [ MANIFEST ]
THE MANIFEST FIELDS
{
"sample": true,
"release": "example-02",
"algorithm": "SHA-256",
"files": [
{
"path": "index.html",
"bytes": "calculated UTF-8 byte length",
"mime": "text/html",
"sha256": "calculated 64-character hexadecimal digest"
}
]
}This is a shape reference. In the downloaded manifest, bytes is a number and sha256 is the calculated digest. The complete manifest always contains all three files, regardless of the tree search.
WHAT IS HASHED?
The exact file content is encoded as UTF-8 with TextEncoder and hashed using SHA-256. The downloaded file uses the same content, so an independent checksum should match the manifest.
VERSION COMPARISON
Compare uses the same path in the other example release. The stylesheet is unchanged; HTML and JavaScript differ. Matching checksums describe identical bytes, not equivalent behaviour.
SECURE CONTEXT
Checksum generation uses the browser cryptography interface. On HTTPS it is available without an account. If the browser does not support it, the repository explains that limitation instead of displaying an invented digest.