Package-level declarations

Types

Link copied to clipboard

Augments the JSModuleProvider interface with support infrastructure for synthetic CommonJS imports; in this case, modules are rendered to strings, which are loaded through a synthetic TruffleFile. This is useful for making built-in modules accessible via a single and uniform interface through both ESM and CJS.

Link copied to clipboard
Link copied to clipboard

Registry for module loaders which are used as "delegates" during the module loading process; such delegates filter based on the requested module names or paths.

Link copied to clipboard
data class JavaScriptCompilerConfig(val sourceMaps: Boolean = true) : Precompiler.Configuration
Link copied to clipboard

Static utilities for internal engine use. Manages initialization of key components within Elide's integration with GraalJs; this includes installing the ElideJsModuleRouter.

Link copied to clipboard

Bridges via JNI to the OXC parsing and code-generator tools.

Link copied to clipboard
fun interface JSModuleProvider

This interface is implemented for classes which can resolve built-in JavaScript modules; usually, a module provider is paired with (or is also a) SyntheticJSModule. The module provider is responsible for bootstrapping or loading the module, as needed, and then providing an instance which satisfies the import request.

Link copied to clipboard
open class JSRealmPatcher
Link copied to clipboard
Link copied to clipboard

Configures native JavaScript/TypeScript parsing and compilation via Oxc.

Link copied to clipboard

Describes a "synthetic" JavaScript module, which is a module that surfaces as a built-in for guest JavaScript code, and which is typically implemented in Kotlin or generally on JVM. Synthetic modules are resolved at their built-in name and routed to the appropriate implementation.