Every Thursday: No frills, no click-through, no spam.

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #282
This week in Elixir

Best Error Monitoring Services for Elixir Phoenix
Jack researched the best Elixir error monitoring services to notify you when users find bugs in production. Check out it so you can deploy with confidence and easily manage errors in your Phoenix apps.

Elixir 1.13 - The Developer’s Point Of view
Bartosz's take on the latest changes to Elixir.New map support, information logging level and changes inside Inspect and more ...

TIL: How to Remove Unused Dependencies from mix.lock
What if a dependency is no longer needed? One library less is potentially one place of conflict between different versions of dependencies less. You can do it with one command, and clear your lock file. Check on:

Building a Simple Calendly Clone with Phoenix LiveView (pt. 5)
This is part five of the Building a simple Calendly clone with Phoenix LiveView series.

Hex v1.0 and the Future of Hex
This is an interesting take by the Hex core team on how Hex will evolve with version 2.0 now that v1.0 is out.

That's it for this round, have a great day!
@rrrene from ElixirWeekly

If you like this newsletter, please tell the world!

You can view this issue in your web browser.

You can subscribe below:

Questions & Answers

Can I submit things I made to be included in the next issue?

Yes! Simply post them to ElixirStatus and you can be sure that they land on my radar.

Is my email address safe with you?

Yes. I'd like to consider myself a trustworthy individual, but then who doesn't?

I am, however, an active member of the open-source Elixir community and the maintainer of Credo and ElixirStatus. I will NOT ruin my reputation by selling your data to a third party.

Why do you require me to confirm my email address?

I just believe that requiring double opt-in to subscribe to any email-based system is a win for both parties: You are safe from unintentionally subscribing and I can be confident that you actually own the email address and want to receive the newsletter I send you :)


Feedback? Questions? Anything else?

Please contact René Föhring (email or tweet @rrrene for a quick conversation).