---
package: "@webjsdev/core"
version: 0.7.2
date: 2026-05-31T16:00:00+05:30
commit_count: 2
---
## Performance

- **serve the browser runtime as a single bundle** ([#148](https://github.com/webjsdev/webjs/pull/148)) [`1b072e1`](https://github.com/webjsdev/webjs/commit/1b072e1)
  The dist build no longer code-splits core into per-subpath entries plus
  shared chunks. It ships one self-contained `webjs-core-browser.js` that the
  bare `@webjsdev/core` specifier and the `/directives`, `/context`, `/task`,
  and `/client-router` subpaths all resolve to, so a dist-mode page makes a
  single cacheable framework request with no chunk-discovery waterfall.
  `/lazy-loader` stays its own on-demand file; static / elided pages still ship
  zero core.

## Fixes

- **never hard-reload against an empty importmap build id** ([#147](https://github.com/webjsdev/webjs/pull/147)) [`8853e0a`](https://github.com/webjsdev/webjs/commit/8853e0a)
  The client router treats an empty or absent `data-webjs-build` on either side
  as "version unknown" and stays on a soft swap instead of a full page reload
  (the importmap-textContent fallback is dropped). A genuine cross-deploy still
  reloads, since both sides then carry non-empty, differing ids. This stops a
  runtime-first-boot server's warmup window from hard-reloading mid-interaction
  and wiping a half-filled form.
