# What's New

## 10-Nov-2025 - v2.0.0 Major Release

SSE v2.0.0 introduces significant improvements with new base classes and automatic context detection.

### Package Renamed

* **@sygnal/sse** → **@sygnal/sse-core**
* Update your `package.json` and all import statements

### New Base Classes with Automatic Context

* **PageBase** - Automatic Webflow page context detection
  * Access `this.pageInfo` with pageId, siteId, collectionId, itemSlug, etc.
  * No manual DOM queries needed
* **ComponentBase** - Automatic element context detection
  * Access `this.element` and `this.context` automatically
  * Component metadata pre-populated

### Improved Lifecycle Methods

* **onPrepare()** - Synchronous setup (replaces `setup()`)
* **onLoad()** - Asynchronous execution (replaces `exec()`)
* More intuitive naming aligned with web lifecycle

### Singleton Pattern for Page Access

* Components can access current page via `PageBase.getCurrentPage()`
* Type-safe with generic support
* Eliminates duplicate context detection

### Critical Fix: RouteDispatcher Instance Persistence

* RouteDispatcher must now be created once and reused
* Prevents data loss between setup and execution phases
* See migration guide for updated pattern

### Backward Compatibility

* Old `IModule` interface still supported for advanced use
* Recommended: Migrate to new base classes for automatic features

See the [sse-template README](https://github.com/sygnaltech/sse-template) for detailed migration examples.

## 29-Jun-2024

* Deployed `@sygnal/sse` core functionality as an NPM package, so that core SSE functionality can be updated independently of the site-specific implementations.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://engine.sygnal.com/whats-new.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.