renderToReadableStream not found in react-dom/server #868

garybaines · 2023-07-27T11:12:35Z

Describe the Bug

We are testing out react-email for use in our project, but getting this error when trying to deploying a test template:

yarn start
yarn run v1.22.19
$ serverless offline --httpPort 4051 --stage local --host 0.0.0.0
serverless-offline-ssm checking serverless version 3.33.0.
✖ in ../node_modules/@react-email/components/node_modules/@react-email/render/dist/index.mjs 31:23-45
    export 'renderToReadableStream' (imported as 'renderToReadableStream') was not found in 'react-dom/server' (possible exports: renderToNodeStream, renderToPipeableStream, renderToStaticMarkup, renderToStaticNodeStream, renderToString, version)

Template code:

import React from 'react'
import {
  Body,
  Head,
  Heading,
  Container,
  Html,
  Text,
} from '@react-email/components'

interface AccessRequestParams {
  testName: string
}

export const accessRequestExpiryTemplate = ({
  testName,
}: AccessRequestParams) => (
  <Html>
    <Head />
    <Body>
      <Container>
        <Heading>TEST</Heading>
        <Text>Here are the details of the request:</Text>
        <Text>{testName}</Text>
      </Container>
    </Body>
  </Html>
)

export default accessRequestExpiryTemplate

Package.json versions

    "dependencies": {
    "@react-email/components": "^0.0.7",
    "react-email": "^1.9.4",
    "react": "18.2.0",
    "react-dom": "^18.2.0",
    "react-router-dom": "^6.11.2",
    "react-tooltip": "4.2.21",
  }

Which package is affected (leave empty if unsure)

@react-email/components

Link to the code that reproduces this issue

n/a

To Reproduce

Deploy with the listed package versions -
We're using serverless: '"start": "serverless offline --httpPort 4051 --stage local --host 0.0.0.0"'

Expected Behavior

The code should compile cleanly without this import error

What's your node version? (if relevant)

18.13.0

The text was updated successfully, but these errors were encountered:

Moicky · 2023-08-03T18:02:46Z

Same issue here.

Problem most likely is, that this is only supported on environments which support WebStreams. This makes it impossible to run on some backends.

docs

Moicky · 2023-08-03T18:47:49Z

Maybe this helps someone:

I needed a quick fix since my webpack kept crashing due to this function not being available in my NodeJS environment.

I used NormalModuleReplacementPlugin to provide a fake implementation since this function is not used in my app:

/* webpack.config.js */

const path = require("path");
const { NormalModuleReplacementPlugin } = require("webpack");

module.exports = {
  // ...
  plugins: [
    new NormalModuleReplacementPlugin(
      /email\/render/,
      path.resolve(__dirname, "./src/renderEmailFix.js"),
    ),
  ],
  // ...
};

// @ts-nocheck
const { renderToStaticMarkup } = require("react-dom/server");

module.exports.render = (component) => {
  const doctype =
    '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">';
  const markup = renderToStaticMarkup(component);
  return `${doctype}${markup}`;
};

shellscape · 2023-09-20T16:12:58Z

Here's what the fix for this looks like shellscape/jsx-email@2eeebfc

Burry · 2023-10-20T15:54:42Z

For me this issue pops up with the latest Next.js release v13.5.6, which bumped the version of React it uses

subvertallchris · 2023-10-26T17:17:45Z

I've been using this happily with Next.js 13.5.6 but it fails immediately on upgrade to Next.js 14.0.0.

subvertallchris · 2023-10-26T17:38:42Z

Here's what the fix for this looks like shellscape/jsx-email@2eeebfc

Thank you so much @shellscape! Here is a patch file that implements this for @react-email/render

diff --git a/node_modules/@react-email/render/dist/index.mjs b/node_modules/@react-email/render/dist/index.mjs
index 27cc390..99fd935 100644
--- a/node_modules/@react-email/render/dist/index.mjs
+++ b/node_modules/@react-email/render/dist/index.mjs
@@ -26,9 +26,19 @@ var renderAsPlainText = (component, _options) => {
 // src/renderAsync.ts
 import { convert as convert2 } from "html-to-text";
 import pretty2 from "pretty";
-import { renderToReadableStream, renderToStaticMarkup as renderToStaticMarkup2 } from "react-dom/server";
+
+import react from 'react-dom/server';
+
+const { renderToStaticMarkup, renderToStaticMarkup: rendertoStaticMarkup2 } = react;
+const renderToStream =
+  // Note: only available in platforms that support WebStreams
+  // https://react.dev/reference/react-dom/server/renderToString#alternatives
+  react.renderToReadableStream ||
+  // Note: only available in Node
+  react.renderToPipeableStream;
+
 async function renderToString(children) {
-  const stream = await renderToReadableStream(children);
+  const stream = await renderToStream(children);
   const html = await readableStreamToString(
     stream
   );

natedunn · 2023-10-26T17:57:21Z

Can confirm this completely breaks on Next 14.0.0

shellscape · 2023-10-26T18:15:41Z

@subvertallchris no prob. fwiw we've completely moved away from using react for rendering, which makes it fully compatible with edge and all fe frameworks. using react for rendering was a big footgun

TaylorFacen · 2023-10-26T21:14:32Z

Confirming that react email worked fine until upgrading to next 14.

JP-HoneyBadger · 2023-10-27T02:32:01Z

Following, exited to get rid of experimental in next.config.js I updated to 14 and now get ./node_modules/@react-email/render/dist/index.mjs
Attempted import error: 'renderToReadableStream' is not exported from 'react-dom/server' (imported as 'renderToReadableStream').

DarrylBrooks97 · 2023-10-27T04:29:10Z

Yup this breaks on upgrade to Next 14 🙃

alexanderbnelson · 2023-10-27T04:38:22Z

Yes indeed, very much busted on Next 14.

martinez-hugo · 2023-10-27T06:56:46Z

So now there are no patch/fix solution for react-email with Next 14 ?

yannxaver · 2023-10-27T06:56:59Z

@subvertallchris no prob. fwiw we've completely moved away from using react for rendering, which makes it fully compatible with edge and all fe frameworks. using react for rendering was a big footgun

My experience with https://github.com/shellscape/jsx-email has been good so far. It's easier to set up the preview server and bugs get fixed quickly if you offer a reproduction.

callumthomson · 2023-10-27T07:33:16Z

Also unable to get working with NextJS 14

bricesuazo · 2023-10-27T08:01:39Z

Is there any progress on this that would allow us to monitor its status?

themendelson · 2023-10-27T11:42:52Z

If anyone is looking for a temporary NextJS 14 fix (using @Moicky's solution)

in next.config.js add these imports:

const path = require("path");
const {
    NormalModuleReplacementPlugin
} = require("webpack");

& add this webpack configuration somewhere in the file:

    webpack: (
        config, {
            buildId,
            dev,
            isServer,
            defaultLoaders,
            nextRuntime,
            webpack
        }
    ) => {
        config.plugins = config.plugins || []
        config.plugins.push(new NormalModuleReplacementPlugin(
            /email\/render/,
            path.resolve(__dirname, "./renderEmailFix.js"),
        ))
        // Important: return the modified config
        return config
    }

Finally, create a new file renderEmailFix.js in the root folder with this code:

// @ts-nocheck
const {
    renderToStaticMarkup
} = require("react-dom/server");

module.exports.render = (component) => {
    const doctype =
        '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">';
    const markup = renderToStaticMarkup(component);
    return `${doctype}${markup}`;
};

subvertallchris · 2023-10-27T11:50:34Z

The patch file I posted yesterday is also working fine for me.

…

On Fri, Oct 27, 2023 at 7:43 AM themendelson ***@***.***> wrote: If anyone is looking for a temporary NextJS 14 fix - in next.config.js add these imports: const path = require("path"); const { NormalModuleReplacementPlugin } = require("webpack"); & add this webpack configuration somewhere in the file: webpack: ( config, { buildId, dev, isServer, defaultLoaders, nextRuntime, webpack } ) => { config.plugins = config.plugins || [] config.plugins.push(new NormalModuleReplacementPlugin( /email\/render/, path.resolve(__dirname, "./renderEmailFix.js"), )) // Important: return the modified config return config } Finally, create a new file renderEmailFix.js in the root folder with this code: // @ts-nocheck const { renderToStaticMarkup } = require("react-dom/server"); module.exports.render = (component) => { const doctype = '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">'; const markup = renderToStaticMarkup(component); return `${doctype}${markup}`; }; — Reply to this email directly, view it on GitHub <#868 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7IJ53PGXWRVS2V5WLVRATYBOM4RAVCNFSM6AAAAAA2Z5JI52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBSG43TCOJRG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

zenorocha · 2023-10-27T16:21:33Z

We're currently working on a fix for that. Will keep you all posted.

thevuong · 2023-10-28T03:59:50Z

We're currently working on a fix for that. Will keep you all posted.

The new release doesn't work because in package.json appears workspace:*

https://www.npmjs.com/package/@react-email/components?activeTab=code

jlison · 2023-10-29T20:45:03Z

If you're facing difficulties after upgrading to Next.js 14, you may find this workaround useful. I created a new utility function called renderEmailHtml.ts, that follows a very similar approach to render-async

// @utils/renderEmailHtml.ts

import type {ReactElement} from 'react';
import type {ReactDOMServerReadableStream} from 'react-dom/server';

async function readStream(readableStream: ReactDOMServerReadableStream) {
  const reader = readableStream.getReader();
  const chunks: AllowSharedBufferSource[] = [];

  while (true) {
    const {value, done} = await reader.read();
    if (done) {
      break;
    }
    chunks.push(value);
  }

  return chunks.map((chunk) => new TextDecoder('utf-8').decode(chunk)).join('');
}

export async function renderEmailHtml(component: ReactElement) {
  // @see https://github.com/vercel/next.js/issues/43810#issuecomment-1462075524
  // Dynamically import ReactDOMServer to circumvent:
  // "Unable to import react-dom/server in a server component"
  const reactDOMServer = (await import('react-dom/server')).default;
  // Note: only available in platforms that support WebStreams
  // https://react.dev/reference/react-dom/server/renderToString#alternatives
  const renderToStream =
    reactDOMServer.renderToReadableStream ||
    reactDOMServer.renderToPipeableStream;

  const doctype =
    '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">';

  const readableStream = await renderToStream(component);
  const html = await readStream(readableStream);
  html
    // Remove leading doctype becuase we add it manually
    .replace(/^<!DOCTYPE html>/, '')
    // Remove empty comments to match the output of renderToStaticMarkup
    .replace(/<!-- -->/g, '');

  return `${doctype}${html}`;
}

Note
☝️ See how we are dynamically importing react-dom/server
(vercel/next.js#43810 (comment)) to circumvent the error:
"Unable to import react-dom/server in a server component"

Usage in, for example, GET app/api/email/welcome/route.ts

// @app/api/email/welcome/route.ts
import Welcome from '@emails/Welcome';
import {renderEmailHtml} from '@utils/renderEmailHtml';

export const runtime = 'edge';

export async function GET() {
   // ...
  const emailHtml = await renderEmailHtml(
    Welcome({name}),
  );
  // ...
}

That solution worked for me.

bukinoshita · 2023-10-30T03:09:14Z

I'm wondering what's your setup, if one can confirm how are you using? I'm testing this way in next.js 14

import { render } from '@react-email/render';
import { MyEmail } from '../../../emails/my-email';
import { NextResponse } from 'next/server';

export const runtime = 'edge'

export const GET = async () => {
  const html = await render(MyEmail());
  return NextResponse.json({ html }, { status: 200 })
}

darasus · 2023-10-30T06:36:11Z

@bukinoshita I think using render package in any node/edge environment would cause this. (personally using nodejs).

I think problem also occurs when just installing render package with pnpm.

devrsi0n · 2023-10-30T13:35:06Z

I'm using the plain fetch as a work around, here is an example from the official doc:

import { NextResponse } from 'next/server';

export const runtime = 'edge';
export const dynamic = 'force-dynamic';

const RESEND_API_KEY = 're_123456789';

export async function POST() {
  const { renderToStaticMarkup } = await import('react-dom/server');
  const res = await fetch('https://api.resend.com/emails', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'Authorization': `Bearer ${RESEND_API_KEY}`,
    },
    body: JSON.stringify({
      from: 'Acme <onboarding@resend.dev>',
      to: ['delivered@resend.dev'],
      subject: 'hello world',
      html: renderToStaticMarkup(<Email />),
    }),
  });

  if (res.ok) {
    const data = await res.json();
    return NextResponse.json(data);
  }
}

bukinoshita · 2023-10-30T14:01:32Z

Can you try using the canary version of render to see if this is still happening?

{
  ...,
  "@react-email/render": "0.0.9-canary.0",
}

nnennajohn · 2023-11-01T23:50:43Z

+1 for jsx-email. Worked on first try. No additional installations, various errors and long debugging. Thanks to those that recommended it. I updated to react-email 9 and resend 2 and still had multiple errors. Decided to give jsx-email a try from all the comments here.

jorvixsky · 2023-11-03T20:22:44Z

Just in case the fix from PR #1009 does not work for someone using Next.js 14: I figured out that the last version of @react-email/render is not installing automatically.

You need to go to package.json under the .email folder that is automatically created and upgrade @react-email/render to 0.0.9. Also I upgraded postcss to 8.4.21 (was unmet dependency for the version that is automatically installed, 8.4.19)

I also removed the appDir experimental function from next.config.js (again, under the .email folder) - as according to Next is no longer valid.

With this changes now works perfectly.

clodal · 2023-11-04T10:19:51Z

As @bukinoshita mentioned, the fix is in @react-email/render@0.0.9

We'll just need to upgrade your local @react-email/render package from "0.0.7" to "0.0.9".

In ./react-starter-email/package.json, pin the @react-email/render version to 0.0.9 using resolutions and also bump the dep versions for good measure:

// ./react-starter-email/package.json
{
  "dependencies": {
    "@react-email/components": "0.0.11",
    "react-email": "1.9.5"
  },
  "resolutions": {
    "@react-email/render": "^0.0.9"
  }
}

Do npm/yarn/pnpm install to apply the change.
Done.

nicitaacom · 2023-11-04T16:06:18Z

Thank you - your solution works for me

pjborowiecki · 2023-11-05T00:34:23Z

None of the options above worked for me.

I might have found a solution though: installing components separately, rather than using @react-email/components. So I have them in my package.json like this now:

    "@react-email/body": "^0.0.4",
    "@react-email/button": "^0.0.11",
    "@react-email/container": "^0.0.10",
    "@react-email/head": "^0.0.6",
    "@react-email/html": "^0.0.6",
    "@react-email/preview": "^0.0.7",
    "@react-email/section": "^0.0.10",
    "@react-email/tailwind": "^0.0.12",
    "@react-email/text": "^0.0.6",

Everything works great and builds with no errors, even with the latest version of resend (2.0.0). I am using Next 14.0.1. Hope that helps someone! I spent way too much time trying to fix react-email and resend related errors lately

catalinpit · 2023-11-06T12:05:13Z

As @bukinoshita mentioned, the fix is in @react-email/render@0.0.9

We'll just need to upgrade your local @react-email/render package from "0.0.7" to "0.0.9".

In ./react-starter-email/package.json, pin the @react-email/render version to 0.0.9 using resolutions and also bump the dep versions for good measure:
// ./react-starter-email/package.json
{
  "dependencies": {
    "@react-email/components": "0.0.11",
    "react-email": "1.9.5"
  },
  "resolutions": {
    "@react-email/render": "^0.0.9"
  }
}
Do npm/yarn/pnpm install to apply the change.

Done.

Unfortunately, it doesn't work for me... neither does the above one...

blakebullis · 2023-11-06T14:13:31Z

I struggled with the initial guidance as well, I did a lot of tinkering, and this is what I currently have that got it working. Unfortunately, I cannot explain why it works now.

"@react-email/components": "^0.0.11" // this broke Button component pY and pX props, you will need to update
"@react-email/render": "^0.0.9-canary.2"
"next": "14.0.2-canary.6"

Resend you mail provider?
"resend": "^2.0.0-canary.2"
if you use Resend: I had to bump this too.

Minor changes are required here around chaining methods. Resend.emails.send() instead of Resend.sendEmail() Also change react: to html: now that you are using renderAsync to generate the HTML of the email.`

nvegater · 2023-11-06T14:50:15Z

I also moved to jsx-email. Way better and is not breaking. Migration took 10 minutes.

catalinpit · 2023-11-07T11:12:28Z

"@react-email/render": "^0.0.9-canary.2"

Thanks! This didn't work either... :-(

issamlk1 · 2023-11-07T13:13:03Z

updating @react-email/render from 0.0.7 to "@react-email/render": "^0.0.9", (with --force)

worked for me,

just to mention @blakebullis comment about the break in pY pX properties in buttons, it also happened to me.
but I think the fix is very easy it's only padding that could be added directly into the style, I guess, let's hope it's not something else and my email didn't got messed up.

bukinoshita · 2023-11-07T16:45:39Z

render

If you're still having issues with renderToReadableStream on @react-email/render, you should upgrade the @react-email/render to v0.0.9 (latest).

Eg:

import { renderAsync } from '@react-email/render'

const html = async renderAsync(EmailTemplate({ firstName: 'John' }))

components

If you're still having issues with renderToReadableStream on @react-email/components, you should upgrade the @react-email/components to v0.0.11 (latest).

Eg:

import { renderAsync } from '@react-email/components'

const html = async renderAsync(EmailTemplate({ firstName: 'John' }))

resend

If you're still having issues with renderToReadableStream on resend, you should upgrade the resend to v2.0.0 (latest).

Eg:

const { data, error } = await resend.emails.send({
  from: 'team@example.com',
  to: 'delivered@resend.dev',
  subject: 'Hello!',
  react: EmailTemplate({ firstName: 'John' })
})

Still having issues after upgrading

If you're using render or components, please provide a code example and your setup (a reproducible repository works better)
If you're using resend, please follow up in the resend-node repository

catalinpit · 2023-11-08T15:16:56Z

Okay, the solution was simpler than expected.

Even though I updated package.json with the appropriate version, the package-lock.json contained the older versions, and the app somehow picked those (something something about the node module resolution algorithm).

To fix this, I added the line "@react-email/render": "0.0.9" both under the "dependencies" and "overrides" in the root package.json. It now forces all references to that package to use v0.0.9

Many thanks to @lxunos for the fix/lesson. 🙏

gjohnsx · 2023-11-08T18:23:38Z

Okay, the solution was simpler than expected.

Even though I updated package.json with the appropriate version, the package-lock.json contained the older versions, and the app somehow picked those (something something about the node module resolution algorithm).

To fix this, I added the line "@react-email/render": "0.0.9" both under the "dependencies" and "overrides" in the root package.json. It now forces all references to that package to use v0.0.9

Many thanks to @lxunos for the fix/lesson. 🙏

This actually worked, thanks! Delete package-lock and node_modules, npm i, and it's working.

julioDazza · 2023-11-13T12:52:13Z

Hey Guys, Those who use the Resend library, update to V2.0.0, it works in Next14. https://www.npmjs.com/package/resend

inventive-username · 2023-11-14T21:59:57Z

No luck with any of the above packages. What magic are you all using? 😂
Also on next14, with overrides and all.

catalinpit · 2023-11-15T06:58:54Z

No luck with any of the above packages. What magic are you all using? 😂 Also on next14, with overrides and all.

Ops, you're in for a rough one then. 👀

bukinoshita · 2023-11-15T16:29:45Z

No luck with any of the above packages. What magic are you all using? 😂 Also on next14, with overrides and all.

Is there a reproducible code?

espressom · 2023-11-27T18:41:02Z

@catalinpit I was able to resolve the issue as well. Thank you.
Below is the method I applied:

Navigate to the .react-email directory and then delete the package-lock.json and yarn.lock files.
Modify @react-email/render in package.json from "0.0.7" to "0.0.9".
Run yarn

henriquepaulalima · 2023-12-02T13:04:38Z

I tried the solutions above but none of it worked, I just manage to solve downgrading my packges and changing some setting on the next.config.js

My package.json looked like this:

{
"scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint",
    "email": "email dev --dir src/emails"
  },
  "dependencies": {
    "@react-email/components": "0.0.6",
    "next": "^13.4.4",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "react-email": "1.9.3",
    "react-is": "^18.2.0",
  },
  "devDependencies": {
    "@types/node": "^17.0.45",
    "@types/react": "^18.2.7",
    "@types/react-dom": "^18.2.4",
    "typescript": "^5"
  }
}

And my next.config.js like this:

/** @type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: true,
  experimental: {
    appDir: true,
  },
}

export default nextConfig

After changing these files, deleting node_modules, .react-email, package-lock.json and running npm i and npm run email the project worked just fine

onlyhasbi · 2023-12-03T15:20:53Z

What i do to resolve the issue

delete folder generated by react-email .react-email | .react-email-temp
delete node_modules
run npm i
install @react-email/render
then npm email

AlecRust · 2023-12-03T15:23:48Z

Installing @react-email/render in addition to the packages I already had installed, fixed it for me too.

BlakePro · 2023-12-09T05:29:30Z

I resolve the issue using in next.config.js

  experimental: {
    serverComponentsExternalPackages: ['@react-email/render', '@react-email/tailwind']
  }

monzim · 2023-12-09T09:23:27Z

It worked for me

    "@react-email/components": "^0.0.11",
    "@react-email/render": "0.0.9-canary.2",

my nextjs version: "next": "14.0.4",

dewodt · 2023-12-11T17:30:47Z

It worked for me
    "@react-email/components": "^0.0.11",
    "@react-email/render": "0.0.9-canary.2",
my nextjs version: "next": "14.0.4",

It works for me, Thank you.

coleerikson · 2024-01-06T22:34:39Z

Confirmed on "@react-email/render": "0.0.10" as well

ndanyikevin · 2024-11-14T18:31:23Z

I want to cry. None of the above is working.

gabrielmfern · 2024-11-14T18:42:23Z

@ndanyikevin This is definitely going to work smoothly on the latest version for @react-email/render, I'd recommend you update.

ndanyikevin · 2024-11-15T05:17:18Z

It worked!!! But I don't know which one finally 🤣🤣🤣

garybaines added the Type: Bug Confirmed bug label Jul 27, 2023

michael-dickinson-sainsburys added a commit to michael-dickinson-sainsburys/react-email that referenced this issue Sep 6, 2023

Fix resend#868 by importing function correctly.

f3a0e37

gustavo-depaula mentioned this issue Sep 20, 2023

fix(render): Import renderAsync function #912

Closed

Chia1104 mentioned this issue Oct 27, 2023

fix(www): using html instead of react template Chia1104/chia1104.dev#345

Merged

rvanlaarhoven mentioned this issue Oct 28, 2023

Upgrade of next@14.0.0 #989

Closed

bukinoshita mentioned this issue Nov 1, 2023

fix(render): Render async next 14 #1009

Merged

bukinoshita closed this as completed in #1009 Nov 1, 2023

renderToReadableStream not found in react-dom/server #868

renderToReadableStream not found in react-dom/server #868

Comments

garybaines commented Jul 27, 2023 • edited Loading

Describe the Bug

Which package is affected (leave empty if unsure)

Link to the code that reproduces this issue

To Reproduce

Expected Behavior

What's your node version? (if relevant)

Moicky commented Aug 3, 2023 • edited Loading

Moicky commented Aug 3, 2023 • edited Loading

shellscape commented Sep 20, 2023

Burry commented Oct 20, 2023

subvertallchris commented Oct 26, 2023

subvertallchris commented Oct 26, 2023

natedunn commented Oct 26, 2023

shellscape commented Oct 26, 2023

TaylorFacen commented Oct 26, 2023

JP-HoneyBadger commented Oct 27, 2023

DarrylBrooks97 commented Oct 27, 2023

alexanderbnelson commented Oct 27, 2023

martinez-hugo commented Oct 27, 2023

yannxaver commented Oct 27, 2023

callumthomson commented Oct 27, 2023

bricesuazo commented Oct 27, 2023

themendelson commented Oct 27, 2023 • edited Loading

subvertallchris commented Oct 27, 2023 via email

zenorocha commented Oct 27, 2023

thevuong commented Oct 28, 2023 • edited Loading

jlison commented Oct 29, 2023 • edited Loading

bukinoshita commented Oct 30, 2023

darasus commented Oct 30, 2023

devrsi0n commented Oct 30, 2023 • edited Loading

bukinoshita commented Oct 30, 2023

nnennajohn commented Nov 1, 2023

jorvixsky commented Nov 3, 2023 • edited Loading

clodal commented Nov 4, 2023 • edited Loading

nicitaacom commented Nov 4, 2023

pjborowiecki commented Nov 5, 2023

catalinpit commented Nov 6, 2023

blakebullis commented Nov 6, 2023 • edited Loading

nvegater commented Nov 6, 2023

catalinpit commented Nov 7, 2023

issamlk1 commented Nov 7, 2023

bukinoshita commented Nov 7, 2023

render

components

resend

Still having issues after upgrading

catalinpit commented Nov 8, 2023

gjohnsx commented Nov 8, 2023

julioDazza commented Nov 13, 2023

inventive-username commented Nov 14, 2023

catalinpit commented Nov 15, 2023

bukinoshita commented Nov 15, 2023

espressom commented Nov 27, 2023 • edited Loading

henriquepaulalima commented Dec 2, 2023 • edited Loading

onlyhasbi commented Dec 3, 2023

AlecRust commented Dec 3, 2023

BlakePro commented Dec 9, 2023

monzim commented Dec 9, 2023

dewodt commented Dec 11, 2023

coleerikson commented Jan 6, 2024

ndanyikevin commented Nov 14, 2024

gabrielmfern commented Nov 14, 2024

ndanyikevin commented Nov 15, 2024

garybaines commented Jul 27, 2023 •

edited

Loading

Moicky commented Aug 3, 2023 •

edited

Loading

Moicky commented Aug 3, 2023 •

edited

Loading

themendelson commented Oct 27, 2023 •

edited

Loading

thevuong commented Oct 28, 2023 •

edited

Loading

jlison commented Oct 29, 2023 •

edited

Loading

devrsi0n commented Oct 30, 2023 •

edited

Loading

jorvixsky commented Nov 3, 2023 •

edited

Loading

clodal commented Nov 4, 2023 •

edited

Loading

blakebullis commented Nov 6, 2023 •

edited

Loading

espressom commented Nov 27, 2023 •

edited

Loading

henriquepaulalima commented Dec 2, 2023 •

edited

Loading