Skip to content

Publish packages 🚀#605

Merged
robin-drexler merged 1 commit into
mainfrom
changeset-release/main
May 1, 2026
Merged

Publish packages 🚀#605
robin-drexler merged 1 commit into
mainfrom
changeset-release/main

Conversation

@shopify-github-actions-access

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@remote-dom/[email protected]

Minor Changes

  • #604 7177edb Thanks @justinhenricks! - Flush BatchingRemoteConnection mutations on a microtask by default

    The default batch function used by BatchingRemoteConnection now schedules flushes on a microtask (via queueMicrotask, falling back to Promise.resolve().then(...)) instead of a macrotask via MessageChannel/setTimeout.

    This ensures that DOM mutations made in the remote environment are delivered to the host before any awaited RPC response resolves, avoiding a class of bugs where the host sees an RPC result before the element updates that produced it (for example, a perform() callback setting an error on a field, only to have the host run its post-await logic before that error mutation arrives).

    If you were relying on the previous macrotask behavior, you can restore it by passing a custom batch option, e.g.:

    new BatchingRemoteConnection(connection, {
      batch: (flush) => {
        const channel = new MessageChannel();
        channel.port1.onmessage = () => flush();
        channel.port2.postMessage(null);
      },
    });

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

@kumar303 kumar303 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not too familiar with the release process but the changelogs and everything else looks right 👍

@justinhenricks

Copy link
Copy Markdown
Contributor

Thanks @kumar303 yeah I'm not either, who is?

@robin-drexler

Copy link
Copy Markdown
Member

@justinhenricks

🦋  info Publishing "@remote-dom/core" at "0.0.0-preview-20260427133553"
🦋  error an error occurred while publishing @remote-dom/core: E404 Not Found - PUT https://registry.npmjs.org/@remote-dom%2fcore - Not found 
🦋  error 
🦋  error  '@remote-dom/[email protected]' is not in this registry.
🦋  error 
🦋  error Note that you can also install from a

seems like a permission thing.
Let's take this into slack

@robin-drexler robin-drexler merged commit 3665d97 into main May 1, 2026
13 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants