Immediately after switching the page, it will work with CSR.
Please reload your browser to see how it works.

Source:https://github.com/SoraKumo001/next-streaming

⬅️ MailCatcher runs a super simple SMTP server
iruoy 6 daysReload
A tool like this is very useful, but this one isn't being maintained anymore. MailHog isn't either.

MailPit, MailCrab and smtp4dev are modern alternatives.

https://github.com/axllent/mailpit

https://github.com/tweedegolf/mailcrab

https://github.com/rnwood/smtp4dev

sj26 6 daysReload
Hiya! I'm the maintainer. It's true I don't do much to it these days. But that's because it's complete. There are lots of things I would love to do to improve it. But none of it would dramatically improve what it does. I fix things when they break. But if it ain't broke...

Happy to answer any questions, or be persuaded that something is broken or would be a dramatic improvement :-)

achairapart 6 daysReload
There is also Mailpit[0] in this space. Actively maintained, written in Go, runs from a single static binary, very low footprint.

[0]: https://mailpit.axllent.org/

ldthorne 6 daysReload
Does anyone know of a similar tool for catching SMS messages in local/development environment? My company uses mailtrap[0] in our development environments to give engineers and product managers a tool to preview emails that would otherwise be sent to users and we're looking for a similar tool for the SMS messages that we send via Twilio. I'd love to have a shared "inbox" per-development environment where PMs can see all the SMS messages that would have been sent (namely to whom the message was sent + the content of the SMS). Ideally it'd hook into whatever Twilio SDK your app is using to send messages (Python, in our case) to intercept calls and route them to the sandbox instead.

It seems like Twilio played with this idea with the Twilio Dev Phone project[1] but that project doesn't seem to be actively maintained.

[0] https://mailtrap.io [1] https://github.com/twilio-labs/dev-phone

rietta 6 daysReload
This is a development tool, not production. For it's intended use it is mature. There has been Git activity within the last year so I am not sure why that would be considered unmaintained by some.

If something is important to someone in particular, they should implement a pull request or see the author's website about making a donation or paying for the development of a particular capability.