Abstract

A method is disclosed for a container readiness check that certifies the browser client a workload serves, not only the process serving it. A check executable, run with the serving container's existing runtime, reads the content directory the server serves and reports not ready unless the server's health endpoint answers success, every inline script block of the served entry document compiles — classic blocks by constructing a compiled-script object that runs nothing, module blocks through the runtime's syntax-check-only mode — and every module-extension file in the served module subdirectory passes the same check. Only after that whole compile stage passes does an execute stage run the classic inline blocks, in document order, in one isolated context whose global object is a forgiving stub of the browser document and host objects. Because a top-level constant is a lexical binding absent from the global object, a generated epilogue appended inside each block's own source exports a primitives-only descriptor of each required binding; the stage fails when a block throws while loading or a required binding is undefined or an empty object or array. Only passing results are cached, keyed by content hash; an advisory mode reports execute failures without gating.

Creative Commons License

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.

Share

COinS