react-email does not support cjs

[paulwer]

What versions are you using? (if relevant)

@react-email/components@x.y.z, react-email@x.y.z, etc.

Describe the Bug

Hello everyone,
we did the upgrade from @react-email/components to use react-email instead as described in the release notes.

As we are using common-js for building this failed at build stage afterwards, because the lib does not support it

Old lib had supported it.

Are there plans to reintroduce common-js again?

What is affected (leave empty if unsure)

No response

Link to the code that reproduces this issue

To Reproduce

{
  "compilerOptions": {
    "module": "commonjs",
    "removeComments": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "allowSyntheticDefaultImports": true,
    "target": "es2019",
    "sourceMap": true,
    "outDir": "./dist",
    "baseUrl": "./",
    "incremental": true,
    "skipLibCheck": true,
    "strictNullChecks": false,
    "noImplicitAny": false,
    "strictBindCallApply": false,
    "forceConsistentCasingInFileNames": false,
    "noFallthroughCasesInSwitch": false,
    "resolveJsonModule": true,
    "jsx": "react-jsx"
  }
}

Expected Behavior

Support common-js

What's your node version? (if relevant)

No response

[gabrielmfern]

This is a regression, common js should keep working.

[gabrielmfern]

At which point did you get an error here exactly? email build or your own build?

Can you please share more info on this?

[paulwer]

at build stage using docker:
this is our docker file:

###################
# BUILD FOR LOCAL DEVELOPMENT
###################

FROM node:22 AS development

# Create app directory
WORKDIR /app

# Copy application dependency manifests to the container image.
# A wildcard is used to ensure copying both package.json AND package-lock.json (when available).
# Copying this first prevents re-running npm install on every code change.
COPY package*.json ./

# copy prisma files
COPY prisma ./prisma/

# Install app dependencies using the `npm ci` command instead of `npm install`
# when installing sharp fails, it should be checked if the binaries are linux specific installed: npm install --os=linux --libc=musl --cpu=x64 sharp
# alternative to try: ENV SHARP_IGNORE_GLOBAL_LIBVIPS=1
RUN npm ci

###################
# BUILD FOR PRODUCTION
###################

FROM node:22 AS build

WORKDIR /app

COPY package*.json ./

# In order to run `npm run build` we need access to the Nest CLI which is a dev dependency. In the previous development stage we ran `npm ci` which installed all dependencies, so we can copy over the node_modules directory from the development image
COPY --from=development /app/node_modules ./node_modules

# Bundle app source
COPY . .

# Run the build command which creates the production bundle
RUN npm run build

# Reducing Dockerimage Size to the minimal required
# TODO: Running `npm ci` removes the existing node_modules directory and passing in --only=production ensures that only the production dependencies are installed. Or usage of `npm prune --omit=dev`. This ensures that the node_modules directory is as optimized as possible. Clearing the cache will also reduce in a smaller size, but currently removes the necessary files from ,prisma/client
RUN npm prune --omit=dev
RUN npm cache clean --force
RUN npm run prisma:generate

###################
# PRODUCTION
###################

FROM node:22 AS production

# Copy the bundled code from the build stage to the production image & copy prisma to allow running migrations
COPY --chown=node:node --from=development /app/prisma ./prisma
COPY --chown=node:node --from=build /app/node_modules ./node_modules
COPY --chown=node:node --from=build /app/assets ./assets
COPY --chown=node:node --from=build /app/dist ./dist

# Set NODE_ENV environment variable
ENV NODE_ENV=production

# Use the node user from the image (instead of the root user)
USER node

# Start the server using the production build
CMD [ "node", "dist/src/main.js" ]

[gabrielmfern]

This worked for me in the latest by just running some CJS code from Node.js by requiring react-email, so while we don't have a reproduction that we can reproduce with here I'm going to close this.