npm / @qwik.dev/partytown
@qwik.dev/partytown
What changed in @qwik.dev/partytown 0.15 to 1, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-19.
1 breaking1 new APIs and options4 behavior and defaults11 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@qwik.dev/partytown 13 changes
Behavior and default changes 1
Partytown exits beta and is now stable.
Fixes and other changes 2
Element interface introspection skips HTMLFencedFrameElement to avoid a Lighthouse deprecated API warning and prevent <fencedframe> creation in the sandbox.
The main thread fallback keeps objects whose properties are forwarded with preserveBehavior, so data pushed before the fallback is not lost.
@qwik.dev/partytown 0.1514 changes
Breaking changes 1
Worker nodes expose only members shared by every Node; elements no longer inherit Text-only members such as splitText.
New APIs and options 1
Properties set on DOM elements by worker scripts are also set on the real elements, with functions calling back into the worker.
Behavior and default changes 3
CSS is defined in the worker; CSS.escape runs there and other members are forwarded to the main thread.
Worker message listeners can reply through MessagePorts sent with the message.
Worker scripts can message cross-origin iframes loaded by the browser, and replies reach the page's message listeners instead of stopping at the Partytown sandbox.
Fixes and other changes 9
For messages from page iframes, event.source is the iframe's window, allowing replies to reach it.
Passing a Request object preserves its method, headers, body, and credentials instead of sending a GET to its URL.
The href property of link and base elements is read and set on the main thread, allowing worker-added stylesheets to load.
Scripts loaded on the main thread now fire worker-registered load and error handlers, including handlers registered with addEventListener.
Calls on an iframe's window from the worker go through its iframe element, including for about:blank frames without a Partytown window on the main thread.
Partytown scripts are not read until the window environment has been sent to the worker, preventing scripts added during page load from failing without being run again.
Tabs starting Partytown in the same millisecond get different tab IDs, preventing a service worker from routing one tab's requests to another.
Window properties whose classes Partytown does not emulate, such as caches and scheduler, return the worker's own object instead of throwing.
Code passed to window.eval in a Partytown script runs in the window's scope, where page globals are defined.