Publish packages 🚀

[shopify-github-actions-access]

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/core@1.11.1

Patch Changes

• #611 f20f6e7 Thanks @eddiechan! - Guard receivers against late mutations on detached nodes

  RemoteReceiver and SignalRemoteReceiver now drop insertChild, removeChild, updateProperty, and updateText mutations whose target node is no longer in the receiver's attached map, instead of throwing a TypeError while dereferencing the missing node.

  This race surfaces in production as unhandled promise rejections such as TypeError: undefined is not an object (evaluating 'x.properties') (Safari) / TypeError: Cannot read properties of undefined (reading 'properties') (V8) when a remote sender dispatches a mutation for a node whose host-side state has just been removed (for example, a removeChild for an ancestor was processed earlier in the same batch, or arrived first from a separate batched payload).

  PR Make removeChild in receivers less strict #533 previously added a similar guard to removeChild for the case where the child slot at a given index was empty, but did not handle the case where the parent itself was missing, and did not touch updateProperty or updateText. This change applies the same defensive pattern uniformly to every connection callback that dereferences attached.get(id).

  Late mutations targeting a detached subtree are by definition no-ops — there is nothing left to mutate.

@remote-dom/signals@2.1.1

Patch Changes

• #611 f20f6e7 Thanks @eddiechan! - Guard receivers against late mutations on detached nodes

  RemoteReceiver and SignalRemoteReceiver now drop insertChild, removeChild, updateProperty, and updateText mutations whose target node is no longer in the receiver's attached map, instead of throwing a TypeError while dereferencing the missing node.

  This race surfaces in production as unhandled promise rejections such as TypeError: undefined is not an object (evaluating 'x.properties') (Safari) / TypeError: Cannot read properties of undefined (reading 'properties') (V8) when a remote sender dispatches a mutation for a node whose host-side state has just been removed (for example, a removeChild for an ancestor was processed earlier in the same batch, or arrived first from a separate batched payload).

  PR Make removeChild in receivers less strict #533 previously added a similar guard to removeChild for the case where the child slot at a given index was empty, but did not handle the case where the parent itself was missing, and did not touch updateProperty or updateText. This change applies the same defensive pattern uniformly to every connection callback that dereferences attached.get(id).

  Late mutations targeting a detached subtree are by definition no-ops — there is nothing left to mutate.

• Updated dependencies [f20f6e7]:

  • @remote-dom/core@1.11.1

example-custom-element@0.0.26

Patch Changes

• Updated dependencies [f20f6e7]:
  • @remote-dom/core@1.11.1

example-getting-started@0.0.26

Patch Changes

• Updated dependencies [f20f6e7]:
  • @remote-dom/core@1.11.1

example-kitchen-sink@0.0.33

Patch Changes

• Updated dependencies [f20f6e7]:
  • @remote-dom/signals@2.1.1
  • @remote-dom/core@1.11.1