what stackpulse tracks
SolidJS releases from GitHub
StackPulse watches SolidJS release notes and keeps the original source link close to every summary.
#stacks/
loading releases…
releases
breaking
security
deprecated
migrations
Simple and performant reactivity for building user interfaces StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches SolidJS release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This release introduces several attribution engine improvements including new timeline records and hooks, fixes cleanup ordering, and renames compiler options. It includes breaking changes to compiler configuration and root disposal behavior.
Developers using compiler options or creating roots within owners need to update their code.
Update compiler configurations and review root creation patterns if creating within owners.
This release introduces new diagnostics for async store setters, consolidates error handling across client and server, and improves hydration behavior. It also moves internal runtime seams behind `solid-js/internal` to clean up the public API surface.
Developers using async store setters, error handling, or internal runtime seams are affected.
Update code to use `onError` for error handling and migrate internal runtime seams to `solid-js/internal`.
This release introduces optimizations for `dynamic()` components, improves error handling context, and addresses compatibility issues with delegated events between Solid 1.x and 2.x. Several breaking changes require attention for users of `<Dynamic>` or custom error handling.
Users of `<Dynamic>`, custom error handling, or delegated events in SolidJS applications are affected by these changes.
Migrate from `<Dynamic>` to `dynamic()` and update any direct accesses to delegated event properties to the new format.
This release introduces a new build tier for observability, moves diagnostics and attribution to separate exports, and enforces ESM-only runtime packages requiring Node 22.12+. It includes breaking changes for pre-release users and developers relying on CommonJS.
Developers using pre-release features, CommonJS, or Node versions below 22.12 are affected.
Upgrade Node to 22.12+ and migrate to ESM if using CommonJS.
This release focuses on improving diagnostics, attribution, and developer tooling with new features like `feedback()` for measuring user wait times and enhanced error reporting. It also deprecates `createTrackedEffect` in favor of more modern alternatives.
Developers using `createTrackedEffect` or relying on specific diagnostics and attribution features in development mode are affected.
Replace `createTrackedEffect` with `createEffect` or `onSettled` as recommended.
This release focuses on improving diagnostics, attribution, and reactivity tracking in SolidJS. Key changes include enhanced feedback mechanisms for user interactions, improved write provenance tracking, and deprecation of `createTrackedEffect`.
Developers using `createTrackedEffect` or deep-importing dev artifacts are affected.
Migrate from `createTrackedEffect` to `createEffect` or `onSettled` and update import paths for dev artifacts.