ElixirWeekly

E-Mail

can't be blank

Making sure you're human: Name your favorite Elixir kernel module!

(can't be blank)

Subscribe

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

Here's what the latest issue looks like:

ElixirWeekly by @elixirstatus

Issue #346

This week in Elixir

Phoenix 1.7 with Npm
Dino blogged on how to use npm to manage all JS dependencies in Phoenix.

Phoenix Dev Blog - Sounds Like a Bug
Chris walks us through diagnosing and fixing an 8-year old LiveView race condition when long-polling in this guided-tour!

Using the Power of Macros for Consistent Authorization
Clemens recently needed to add authorization to a lot of his context modules and wrote this post about his journey.

Even more from around the Elixir community

🟢 Registration Misc

ElixirConf US 2023 Will be Sep 5-8 in Orlando, FL! Conference

Thinking Elixir: Orion for Distributed Tracing in Production Podcast

Deleting LiveView Stream Elements by `dom_id` Video

Long-lived Processes in Elixir Video

The Benefits of Using Elixir for Backend Development: Our Perspective Blog post

phx.tools: Complete Development Environment for Elixir and Phoenix Blog post

Elixir for Humans Who Know Python Blog post

Finitomata ❤ Mox Blog post

Creating a Simple Weather Application with Phoenix LiveView Blog post

Avoiding Data Loss With Elixir Dets Blog post

ExRoseTree - a Rose Tree and Zipper in Elixir with a Slew of Navigation Primitives Project update

Allegro/map-with-indifferent-access Project update

Submit your blog post/project update

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:

E-Mail

can't be blank

Making sure you're human: Name your favorite Elixir kernel module!

(can't be blank)

Subscribe

Questions & Answers

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

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.

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 :)

Contact

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