Conversation
c8e1a10 to
364cac0
Compare
8283f6e to
d57efb4
Compare
|
/snapit |
|
🫰✨ Thanks @robin-drexler! Your snapshots have been published to npm. Test the snapshots by updating your "@remote-dom/core": "0.0.0-snapshot-20241204183932",
"@remote-dom/polyfill": "0.0.0-snapshot-20241204183932",
"@remote-dom/preact": "0.0.0-snapshot-20241204183932",
"@remote-dom/react": "0.0.0-snapshot-20241204183932",
"@remote-dom/signals": "0.0.0-snapshot-20241204183932" |
|
/snapit |
|
🫰✨ Thanks @igor10k! Your snapshots have been published to npm. Test the snapshots by updating your "@remote-dom/core": "0.0.0-snapshot-20241204204334",
"@remote-dom/polyfill": "0.0.0-snapshot-20241204204334",
"@remote-dom/preact": "0.0.0-snapshot-20241204204334",
"@remote-dom/react": "0.0.0-snapshot-20241204204334",
"@remote-dom/signals": "0.0.0-snapshot-20241204204334" |
|
/snapit |
|
🫰✨ Thanks @igor10k! Your snapshots have been published to npm. Test the snapshots by updating your "@remote-dom/core": "0.0.0-snapshot-20241204205017",
"@remote-dom/polyfill": "0.0.0-snapshot-20241204205017",
"@remote-dom/preact": "0.0.0-snapshot-20241204205017",
"@remote-dom/react": "0.0.0-snapshot-20241204205017",
"@remote-dom/signals": "0.0.0-snapshot-20241204205017" |
|
/snapit |
|
🫰✨ Thanks @robin-drexler! Your snapshots have been published to npm. Test the snapshots by updating your "@remote-dom/core": "0.0.0-snapshot-20241204224457",
"@remote-dom/polyfill": "0.0.0-snapshot-20241204224457",
"@remote-dom/preact": "0.0.0-snapshot-20241204224457",
"@remote-dom/react": "0.0.0-snapshot-20241204224457",
"@remote-dom/signals": "0.0.0-snapshot-20241204224457" |
9659e48 to
e9d04ef
Compare
584ccad to
fdd1a75
Compare
fdd1a75 to
590eb6d
Compare
|
/snapit |
|
🫰✨ Thanks @igor10k! Your snapshots have been published to npm. Test the snapshots by updating your "@remote-dom/core": "0.0.0-snapshot-20250107180300",
"@remote-dom/polyfill": "0.0.0-snapshot-20250107180300",
"@remote-dom/preact": "0.0.0-snapshot-20250107180300",
"@remote-dom/react": "0.0.0-snapshot-20250107180300",
"@remote-dom/signals": "0.0.0-snapshot-20250107180300" |
lemonmade
left a comment
There was a problem hiding this comment.
Had a bunch of requests, but this is looking really great 👍
| const index = tree[id]?.findIndex(({slot}) => slot === key) ?? -1; | ||
|
|
||
| if (index !== -1) { | ||
| records.push([ |
There was a problem hiding this comment.
Should we check if the new fragment is actually different from the old one, before removing it?
There was a problem hiding this comment.
Can it be the same? I assume that there's some shallow comparison happening on the remote to not cause redundant payloads. I mean if the fragment didn't change then there should be no "update props" action.
|
/snapit |
|
/snapit |
|
🫰✨ Thanks @igor10k! Your snapshots have been published to npm. Test the snapshots by updating your "@remote-dom/core": "0.0.0-snapshot-20250110191257",
"@remote-dom/polyfill": "0.0.0-snapshot-20250110191257",
"@remote-dom/preact": "0.0.0-snapshot-20250110191257",
"@remote-dom/react": "0.0.0-snapshot-20250110191257",
"@remote-dom/signals": "0.0.0-snapshot-20250110191257" |
Co-authored-by: Chris Sauve <chrismsauve@gmail.com>
kumar303
left a comment
There was a problem hiding this comment.
I think it would be nicer to introduce this as a separate package
packages/core/package.json
Outdated
| }, | ||
| "dependencies": { | ||
| "@remote-dom/polyfill": "workspace:^1.4.2", | ||
| "@remote-ui/core": "^2.0.0", |
There was a problem hiding this comment.
re: https://github.com/Shopify/remote-dom/pull/511/files#r1909454081
It also struck me as "not right" for @remote-dom/core to depend on @remote-ui/core.
What about, instead, extracting all the adapter parts to a new package like @remote-dom/compat? Is it possible to do that? This would allow core to remain focused on remote-dom exclusively while still allowing someone to use @remote-dom/compat if they need remote-ui backwards compatibility.
|
/snapit |
|
🫰✨ Thanks @oluwatimio! Your snapshots have been published to npm. Test the snapshots by updating your "@remote-dom/core": "0.0.0-snapshot-20250115141927",
"@remote-dom/polyfill": "0.0.0-snapshot-20250115141927",
"@remote-dom/preact": "0.0.0-snapshot-20250115141927",
"@remote-dom/react": "0.0.0-snapshot-20250115141927",
"@remote-dom/signals": "0.0.0-snapshot-20250115141927" |
e753b82 to
c409934
Compare
|
/snapit |
|
🫰✨ Thanks @igor10k! Your snapshot has been published to npm. Test the snapshot by updating your "@remote-dom/compat": "0.0.0-snapshot-20250116203606" |
|
Hey folks, just trying to figure out if something is blocking this PR from being shipped? |
|
@simontaisne another review from @lemonmade would be good, I think. |
kumar303
left a comment
There was a problem hiding this comment.
I'm lacking some context on remote-dom internals but it looks good to me. I played with the kitchen sink example and added some fragments to it in various places. Everything was working well ✨
lemonmade
left a comment
There was a problem hiding this comment.
Wonderful job — thank you all for maintaining the high bar for documentation and examples in this repo, and for elevating the bar on unit tests!
packages/compat/package.json
Outdated
| "access": "public", | ||
| "@remote-dom/registry": "https://registry.npmjs.org" | ||
| }, | ||
| "version": "1.0.0", |
There was a problem hiding this comment.
Will the changeset being a major not put this to 2.0.0 on deploy? I assumed you'd want to start on a 0.x version instead.
There was a problem hiding this comment.
I'm not familiar with how versioning works in this repo. My goal was to have a 1.0.0 release for the compat package. Should I put 0.1 here as the version and let changesets bump it to 1.0.0?
There was a problem hiding this comment.
Yes, I think you should do that. IIRC, as soon as you merge to main it will deploy the 0.1.0 version, and then changesets will create an additional PR that will bump it to 1.0.0 and manage the changelogs.
There was a problem hiding this comment.
Thank you for all these helpful, easy-to-read tests 💜
Close https://github.com/Shopify/temp-project-mover-Archetypically-20250512095102/issues/58.
The adapter is supposed to help transition from
remote-uitoremote-dom, while supporting existing legacy code that usesremote-ui-style APIs.