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

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #284
Welcome to Issue #284

This is the last issue for the year.

2021 has been an exciting year for the Elixir community, with the success of Nx and Livebook, to name a few.

One thing that really hypes me is Phoenix's move to ESBuild, so that we no longer need to install Node for web projects. The Tailwind project also released a standalone version of its CSS toolchain (check the blog post below to see how to utilize this in Phoenix).

Let's have a great, less COVID-y 2022 ✌

This week in Elixir

TIL: Log SQL Generated by Ecto Migration
Understanding exactly what SQL commands are running is helpful to ensure safe migrations.

Introducing `for let` and `for reduce`
José shares this idea for two new forms of comprehensions: `for let` and `for reduce` on the ElixirForum.

Adding Tailwind CSS to a Phoenix Project
Koen wrote a quick guide about adding TailwindCSS to a Phoenix project using the standalone binaries.

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