Jayden Seric

Since AWS will gather the whole request in memory before passing it on to your function, any workarounds to try to simulate a request stream for `processRequest` which then buffers...

Thanks for the suggestion! I'm not very familiar with Google Cloud Functions so I'm not in a great position to review the change. @mike-marcacci any thoughts?

A slightly different approach would be to add [a `package.json` `exports` field to allow extensionless conditional CJS/ESM deep imports](https://nodejs.org/api/esm.html#esm_conditional_exports) from `styled-jsx/css`, but there is a lot to consider about adding...

@giuseppeg what do you mean. I already said: > This PR is non-breaking. The imports documented in the readme right now are invalid for Node.js, they just happen to currently...

There is a lot to unpack in your comment. > This is browser code Not true, React components are often rendered in a Node.js environment. All Node.js/npm ecosystem tooling should...

Adding an `exports` field to `package.json` with conditional exports is a breaking change because: 1. Early versions of Node.js that don't support the `exports` field ignore it and fall back...

@huozhi it's great to see some movement towards proper ESM support, thanks for your recent maintenance work and for giving me the opportunity to see this PR through. This PR...

Another few things to support Node.js ESM: - There should be a decoy `styled-jsx/css.mjs` file that throws relevant errors about transpilation having not worked. Having a file there with default...

Nope.

I'll check, but if that is the case, how come none of the styles are broken right now at https://deviceagnosticui.com, or https://jaydenseric.com?