Open JonnyBGod opened 6 months ago
Yea I can confirm this. Upon updating 1.11.2 i get the following error upon startup:
[Nest] 44016 - 29.02.2024, 21:34:11 ERROR [MailerService] Transporter is ready
I am not using any custom transport though.
I can confirm too, my application used SendMailTransport and I received the same errors.
I removed it to use simple object config and I discovered the same error message that @domme1908 referred (see comment above ↑)
Why I always receiving [MailerService] Transporter is ready
?
Me too, please tell me how to solve it?
About the phantom Transporter is ready
this is probably triggered here :
Since this.transporter
is added unconditionally.
@GFoniX bug!!! verify from https://github.com/nest-modules/mailer/pull/1118
Fixed in this PR https://github.com/nest-modules/mailer/pull/1133. Sorry for this inconvenience, I had indeed run npm run test but not with SendGrid. Now, the test has become "optional," and I have added an additional check just in case.
Describe the bug After upgrading to 1.11 or later it faills compilation while using either 'nodemailer-mandrill-transport' or 'nodemailer-mailgun-transport'.
To Reproduce
Expected behavior It should not break compatibility with older transports that use callbacks intead of promises
Additional context