ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →

TypeScript declarations generated from the platform's own Java model

The platform's server-side JavaScript API now ships as generated TypeScript declarations, derived from the Java source model itself, and published as installable packages for editor completion and type checking.

Server-side scripting on the platform is JavaScript against a large API surface implemented in Java. Until now an engineer learned that surface from documentation and from the workbench; the editor could not complete a method it had never been told about. This release generates TypeScript declarations for that API directly from the Java model, so the contract the editor knows is the contract the runtime implements.

Generated from the source model

  • Derived from the documentation model. Declarations are generated from the platform's own source doclet, so the types follow the implementation rather than a parallel hand-maintained file that drifts.
  • Faithful type mapping. A dedicated mapper translates the Java type mirror to TypeScript with parity as its objective, so a generic, an array or a bounded type arrives in the declaration with its meaning intact.
  • Emission metadata at scan time. The scanner captures what each type needs for emission as it walks the source, so generation is a single pass rather than a series of corrections.

Readable output, not just correct output

  • Functional interfaces as function types. An interface with a single abstract method is emitted as a TypeScript function type, so a callback is written as a callback rather than as an object with one method.
  • Names without noise. The disambiguating hash is dropped from every name that does not need one, so the common case reads as the plain type name.
  • Stubs for what is out of scope. A type referenced from outside the generated surface is emitted as an empty stub, so the declaration set resolves without pulling in the entire dependency graph.

Published as packages

  • Installable. The declarations are published as packages, so an editor is configured for the platform's API by installing a dependency.
  • One accessor for the platform database. The generated surface exposes the platform database through a single static accessor in place of the previous constant, so the entry point is discoverable by completion.

The declarations describe the existing API and change no runtime behaviour: scripts written before this release type-check against the generated surface without modification.

See the feature →

← All posts