Is it possible to use .env files?

I have a project with a .env file in the root and I use import "dotenv/config"; to load the .env to process.env. I didn’t realize it at first but this is not working with email/index.ts as the env values I’d expect to be defined (present in my .env) are not set on process.env.

[bruceharrison1984]

Just wanted to add this is a great feature to build in. I had to slightly tweak mine because I use a file with a different name:

import * as dotenv from 'dotenv';
import { buildSendMail } from 'mailing-core';
import nodemailer from 'nodemailer';

dotenv.config({
  path: '.env.local',
  debug: true,
});

Using debug helped me figure out that due to the way I have tsconfig setup, my base path is the root of the repo, and not the location of emails/index.ts. After that, I was up and running with SendGrid in a matter of minutes.

Great job on this, looking forward to see where it goes!

[cymen]

I edited emails/index.ts to change the contents of a console.log and it’s updating without restarting (wasn’t sure if that would be the case) so I’d chalk this up to some kind of odd edge case.

I’ll keep trying to reproduce as I use mailing but I’m fine with closing this out and can reopen if I can get it to happen again. Sorry for what amounts to noise at the moment.

On a side note, really happy to find mailing – thank you for sharing it. I was already using MJML but had a email template compile step and previewing wasn’t as nice as I’d like (and I wasn’t using react-mjml yet as it didn’t fit well in my workflow). But I’m excited to be able to use all of that and have the excellent preview capabilities of mailing!