v1.1.1

@vivari/core

Patch Changes

• 93a6a79 Thanks @maitrungduc1410! - A MessagePort follows Node's rules in the browser: onmessage and addEventListener('message') now start the port and keep the process alive like on('message'), a port stops holding when its other end closes, and a worker's parentPort is a real MessagePort (GitHub issue #13).

Install

npm install @vivari/core@1.1.1 @vivari/react@1.1.1

@vivari/core@1.1.1 · @vivari/react@1.1.1 on npm, dist-tag latest, published with provenance.

Full Changelog: v1.1.0...v1.1.1

v1.1.0

@vivari/core

Minor Changes

• #9 973e503 Thanks @ThailerL! - Add a connection event (with the ConnectionEvent and ConnectionListener types) that fires when one process in the VM opens a TCP connection to a server in another, before either end can send anything. It reports the server's port, the connection's remotePort, both pids, and the client's still-running ancestors.

• #10 525b244 Thanks @ThailerL! - Previews now carry the host page's Document-Isolation-Policy (Chromium), so a same-origin preview lands in the page's agent cluster and its contentWindow.location stays readable. Declare the value with the new BootOptions.documentIsolationPolicy (the DocumentIsolationPolicy type, "none" for no header); left unset, the Service Worker learns it with a HEAD to the page's URL, without its query or fragment and without following redirects. Previews served to a cross-origin IDE (modes B and C) get no policy.

Patch Changes

• #9 973e503 Thanks @ThailerL! - A server accepting a connection from another process in the VM now sees a real socket.remoteAddress and socket.remotePort, which used to be undefined. The kernel picks the client's port from the ephemeral range, unique across the VM while the connection is open, so two processes dialing the same server no longer report the same localPort.

• 4898638 Thanks @maitrungduc1410! - A cross-process TCP dial that finds every client port in use now fails with EADDRNOTAVAIL, as on a real host, instead of ECONNREFUSED.

• #11 700ed05 Thanks @ThailerL! - A hard-reloaded page (Ctrl+Shift+R) has no Service Worker controller, so its previews used to go to the host's origin while boot() reported success. The page now asks the preview Service Worker to claim it. The standalone preview tab of modes B and C, __vv-preview-boot.html, does the same and comes back after a hard reload instead of waiting for a controller that never came.

@vivari/react

Minor Changes

• #9 973e503 Thanks @ThailerL! - Add a connection event (with the ConnectionEvent and ConnectionListener types) that fires when one process in the VM opens a TCP connection to a server in another, before either end can send anything. It reports the server's port, the connection's remotePort, both pids, and the client's still-running ancestors.

Upgrading

This release changes __vv-bridge.html, __vv-preview-boot.html, sw.js, which embedders host on their own origin. After updating the packages:

• If you serve the preview Service Worker yourself, copy node_modules/@vivari/core/dist/assets/sw.js there again. Browsers keep running the old one until it is replaced.
• If you deploy a separate preview origin (modes B and C), redeploy it so its __vv-bridge.html and __vv-preview-boot.html match this version.

Install

npm install @vivari/core@1.1.0 @vivari/react@1.1.0

@vivari/core@1.1.0 · @vivari/react@1.1.0 on npm, dist-tag latest, published with provenance.

Full Changelog: v1.0.3...v1.1.0

Vivari SDK v1.0.3

Vivari SDK v1.0.3 (npm tag latest).

• @vivari/core — framework-agnostic browser WebContainer SDK
• @vivari/react — React <Vivari> component + useVivari() hook

What's Changed

• fix(runtime/net): a failed listen must not unregister the port's real server by @ThailerL in #5
• Fix OPFS delete-then-recreate persistence race by @kkrausse in #8
• feat(net): optional network relay — real tcp both ways, off by default by @maceip in #6

New Contributors

• @ThailerL made their first contribution in #5
• @kkrausse made their first contribution in #8
• @maceip made their first contribution in #6

Full Changelog: v1.0.2...v1.0.3

Vivari SDK v1.0.2

Vivari SDK v1.0.2 (npm tag latest).

• @vivari/core — framework-agnostic browser WebContainer SDK
• @vivari/react — React <Vivari> component + useVivari() hook

Full Changelog: v1.0.1...v1.0.2

Vivari SDK v1.0.1

Vivari SDK v1.0.1 (npm tag latest).

• @vivari/core — framework-agnostic browser WebContainer SDK
• @vivari/react — React <Vivari> component + useVivari() hook

Dry run: false — when true, the .tgz files below were
built and attached but nothing was pushed to npm.

Full Changelog: v1.0.0...v1.0.1

Vivari SDK v1.0.0

Vivari SDK v1.0.0 (npm tag latest).

• @vivari/core — framework-agnostic browser WebContainer SDK
• @vivari/react — React <Vivari> component + useVivari() hook

Full Changelog: https://github.com/maitrungduc1410/vivari/commits/v1.0.0