Release

Coralite v0.33.0 Released

Coralite v0.33.0 introduces a major context architecture overhaul, standardizes the V1 API, implements reactive properties with attribute synchronization, and transitions the codebase license to MPL 2.0.

TD
Thomas David May 13, 2026

Coralite v0.33.0 has arrived, delivering a streamlined context architecture overhaul, V1 API standardization, and new features like reactive properties and performance benchmarking. This release also marks a transition of the framework's license to MPL-2.0.

Context Architecture Overhaul and V1 API

We have simplified the internal and external component APIs to improve developer experience and optimize execution. Localized component and plugin execution contexts are now pruned to essential properties: properties, page, root, module, id, and renderContext. Framework utilities have been removed from the global scope of component scripts. Instead, they are now exposed via synthetic ESM modules (coralite, coralite/plugins, and coralite/utils).

Additionally, we have standardized the defineComponent syntax. The term values (and legacy tokens) has been renamed to properties, ensuring a consistent model for passing and evaluating component attributes.

javascript
Code copied!
  import { defineComponent } from 'coralite';
  
  export default defineComponent({
    properties: {
      greeting: 'Hello, World!'
    },
    script(context) {
      const { properties } = context;
      console.log(properties.greeting);
    }
  });

Reactive Properties and Attribute Synchronization

This release introduces native support for reactive properties. Components can now dynamically evaluate properties and automatically synchronize their values back to the DOM attributes. This provides a clean, predictable bridge between server-rendered markups and client-side hydrations.

High-Performance Micro-Benchmarks and Refactored Plugins

To prevent performance regressions, Coralite v0.33.0 integrates a new micro-benchmarks suite using mitata. This suite tracks performance patterns in separate V8 isolates for processes like AST cloning, plugin state merging, and token interpolation.

The plugin hook architecture has also been refactored. Rather than mutating shared state in-place, hooks now return clean state patches that the engine safely merges. Additionally, a new _triggerPluginAggregateHook handles flattening array collections from plugins cleanly, improving overall reliability.

Licensing Transition to MPL-2.0

To better support community collaboration and enterprise adoption, Coralite and its associated packages are transitioning their license from AGPL-3.0 to the Mozilla Public License 2.0 (MPL-2.0).

Breaking Changes

  • Rename of Values to Properties: Component definitions and contexts now use properties instead of legacy values or tokens.
  • Context Pruning & Globals Removal: Global utilities are no longer injected into component script environments. Explicitly import framework helpers from synthetic modules.
  • Plugin Context Flattening: The helpers namespace has been removed from the plugin execution context; all utilities are now merged directly into the root execution context object.
  • Component Engine Signatures: Internal functions like createComponentElement and _processDependentComponents no longer accept the bulky component parameter, accepting specific page and root structures instead.
  • Node.js Requirement: The minimum supported Node.js version is now >=20.19.0 across all packages.

How to Upgrade

To upgrade to the latest version, update your project dependencies:

bash
Code copied!
  npm install coralite@0.33.0
bash
Code copied!
  npm install coralite-scripts@0.33.0
TD

Thomas David

Creator of Coralite. Writing about the intersection of native web APIs, compiler design, and AI-assisted development.