v0.15.1
Release notes from CHANGELOG.md for @async/framework@0.15.1 (2026-07-06).
- Updated the Flow bridge to consume
@async/flow0.10.3, including the
framework-runtime helper paths required by current Flow releases. - Fixed Flow async signal refresh handlers so a refresh without authored input
uses the signal's configured arguments instead of passing an empty object. - Rolled back partial signal and handler registrations when a Flow mount fails,
preventing failed mounts from leaving stale registry entries behind. - Fixed SSR signal patches for mounted Flow signals so exact paths such as
cart.totalupdate without serializing an unintended parentcartsignal. - Added
./jsx/jsx-runtimeand./jsx/jsx-dev-runtimepackage exports so
jsxImportSource: "@async/framework/jsx"resolves under the automatic JSX
transform; the base entrypoints default to the runtime profile types. - Guarded the Vite plugin bootstrap transform: modules are replaced only when
they actually import@async/framework/jsx*(comment and string mentions no
longer match), replacements are logged, multiple modules collapsed into one
virtual bootstrap now warn, and full-rewrite transforms return an empty
sourcemap instead ofmap: null. - Made the Vite 8 + Rolldown host check use plugin-context metadata
(this.meta.viteVersion/this.meta.rolldownVersion) inconfigResolved
instead of treating the resolved config as a host descriptor, and exported
detectViteHostandimportsAsyncJsxhelpers. - Stopped defaulting
server.basewhen composing@hono/vite-dev-server;
baseis forwarded only when the app sets it, so user-configured Vite
basevalues are no longer overridden by default. - Declared
vite >= 8as an optional peer dependency. - Reported runtime slice
status(availableforsignals/events,
plannedforasync-signals/stream) with aruntime-slice-planned
warning diagnostic, and documented that planned slices are recorded but not
activated by@async/framework/runtimeyet. - Reworked the
vite-jsx-streamingexample onto the buildtime JSX profile so
the authoring source matches the shipped type profiles, and documented that
the fixture profile is the current source of truth for the emitted plan.
Release evidence
- Release type: stable
- Package profile: framework-browser
- npm pack files: 61
| File | Raw | Gzip | Brotli |
|---|---|---|---|
browser.d.ts |
42.8 KB | 7.8 KB | 6.9 KB |
browser.js |
249.7 KB | 46.9 KB | 38.4 KB |
browser.min.js |
105.3 KB | 30.8 KB | 27.1 KB |
browser.ts |
249.8 KB | 46.9 KB | 38.4 KB |
browser.umd.js |
265.3 KB | 48.1 KB | 39.0 KB |
browser.umd.min.js |
106.8 KB | 31.0 KB | 27.2 KB |
framework.d.ts |
44.8 KB | 8.1 KB | 7.2 KB |
framework.ts |
390.1 KB | 72.5 KB | 57.8 KB |
server.js |
390.1 KB | 72.4 KB | 57.7 KB |
Diff links:
- browser.d.ts: https://github.com/async/framework/compare/HEAD%5E...v0.15.1?diff=unified#diff-browser.d.ts
- browser.js: https://github.com/async/framework/compare/HEAD%5E...v0.15.1?diff=unified#diff-browser.js
- browser.ts: https://github.com/async/framework/compare/HEAD%5E...v0.15.1?diff=unified#diff-browser.ts
- browser.umd.js: https://github.com/async/framework/compare/HEAD%5E...v0.15.1?diff=unified#diff-browser.umd.js
- framework.d.ts: https://github.com/async/framework/compare/HEAD%5E...v0.15.1?diff=unified#diff-framework.d.ts
- framework.ts: https://github.com/async/framework/compare/HEAD%5E...v0.15.1?diff=unified#diff-framework.ts
- server.js: https://github.com/async/framework/compare/HEAD%5E...v0.15.1?diff=unified#diff-server.js
Source: CHANGELOG.md in tag v0.15.1.