fix(react-email): Respect user NODE_ENV

[AshotN]

7eb68af#diff-c5c5ee3ee563e33630e1ad83f07d66cb99b9be9a662fa8f4f9d7a6d43e98b7d0

This commit caused NODE_ENV to no longer be respected and always become development

This change will respect NODE_ENV and default to development if nothing is passed in.

[changeset-bot]

🦋 Changeset detected

Latest commit: 3719786

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
react-email	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

@AshotN is attempting to deploy a commit to the resend Team on Vercel.

A member of the Team first needs to authorize it.

[gabrielmfern]

I don't think we can give preference to the process.env like this since it'll always have NODE_ENV as production by default. What is your use case for this change? Maybe we can think of something better

it also seems to cause a type error

[AshotN]

I was trying to deploy the preview site. I am using https://github.com/node-config/node-config to handle my ENV files.

Some of my email templates rely on variables from those env files. With react-email changing the NODE_ENV, I end up being unable to load the files.

[gabrielmfern]

@AshotN Got it, I tested it out a bit and your way works just fine in the situation that I was mentioning.

Have you tested this PR out to see if it fixes it in your case? What you can do to test it out is run pnpm build and then npm link in packages/react-email and then the email CLI is going to be using your local version.

[AshotN]

To be honest, I have not tested it. It seemed like a simple change, but I will spend some time this week making sure.

[AshotN]

@gabrielmfern Sorry for the lag on my response, I just tested it on my local and it does solve my problem. I caught the branch back up. If there is anything else you need from me, let me know. Thanks!