Closed jaumard closed 6 years ago
Bummer, this would need to be refactored so that the transport configuration is consumed versus being set. It makes it less flexible, but more testable unfortunately.
I don't think it's possible to just have the config here as there a lot of plugin for node mailer and I can't manage them all just by config... I didn't try yet to migrate trailpack-passport but maybe I'll have the same problem with strategies set under config :/
A hack is to use a callback customTransporter: () => transport
as it can't be flattened, then no more problems.
Issue Description
The trailpack-email contain this configuration:
The problem is apparently
customTransporter: transport
when trails is trying to flatten the config object, I get this error:Environment
any idea @trailsjs/maintainers ?