Compiler and evidence

Current capabilities and measured limits.

LilScript compiles typed source into JavaScript and selects output against a declared raw, gzip or Brotli objective. The library comparisons connect each claim to exact downloadable files, source identities, configuration, tests and build times.

Optimization and public boundaries

Typed specialization, dead-code elimination and representation changes can remove work when program behavior permits them. Property mangling applies to eligible owned data; public, externally visible and reflective keys constrain those changes. A smaller artifact alone does not establish lower parse time, faster execution or complete API compatibility.

ESM, CommonJS and browser-global delivery are produced by the compiler. Host providers, declarations, CSS, fonts and workers are identified separately in package evidence. Individual ports can include JavaScript providers or upstream runtime components.

Measurement controls

Raw, gzip and Brotli each select an independently compiled LilScript artifact. Each original lane uses the recorded upstream version, export boundary and dependencies. Terser, esbuild and Oxc are measured where listed; the smallest recorded original for that codec is selected.

Build times describe the recorded stages on a shared machine. Original package bundling and minification is not the same workload as compiling its original repository from source. Installation, testing and final file compression are excluded. Repeated quiet-machine measurements are needed for strong throughput claims.

Compatibility limits

Monaco is a partial editor implementation. Solid is an experimental compatibility runtime with missing semantics. PlayCanvas covers shader processing rather than the complete engine. Motion covers DOM APIs and excludes React integration. PostHog combines the original SDK with selected LilScript utility implementations. Each library page states its own tested boundary.

Behavior tests and browser examples accompany the artifacts. Passing selected tests is evidence for those cases, not a proof of complete upstream equivalence.

Inspect and reproduce

Language and configuration · All library evidence · Live examples