Tom Sherman

I do think it's easier to just mount the server component as a client component with createRoot though - this works in react-dom canary today. See commit on your test...

> Also, while I understand why your version of the test needs to await for a suspended render, I'd rather not make end users worry about understanding this if there's...

Do we agree that RTL (at least in the core API) shouldn't support this kind of routing stuff? If so probably best to split that conversation out into a different...

> but when we use asciiToUint8Array we assume the text to encrypt is ascii The browser has this build in via TextEncoder/TextDecoder. https://developer.mozilla.org/en-US/docs/Web/API/Encoding_API

I'm struggling with this also. Reading https://github.com/bluesky-social/atproto/issues/999#issuecomment-1538905166 though it seems like this is mostly on purpose. It's down to the application to validate and narrow this object to something more...

You mentioned it in your previous comment > Maybe it's not the package manager's duty, it's the language's Package management and module visibility are two orthogonal problems.

You can get quite far with git submodules. Zig for example got pretty far with this approach.

I've narrowed this down to https://github.com/aws/aws-sdk-js-v3/blob/6b4bde6f338720abf28b931f8a4506613bd64d3f/packages/util-dynamodb/src/convertToAttr.ts#L12 A fix could look like inserting this at the top of that function: ```js if (typeof data.toJSON === 'function') { data = data.toJSON(); }...

Still an issue, I've created a reproduction: https://github.com/tom-sherman/DynamoDBDocumentClient-circular-reference-bug

This is still a bug. In my reproduction where I want to short circuit the circular reference with toJSON I get a different error on the latest client. Circular refs...