Elm Weekly - Issue #132
Benefits of TDD and unit testing, "Is it my cow?" animations, code design and modules, updated Elm VS Code plugin, browser extensions to parse Debug.log output, a tool to turn Elm output into ES6 modules, and an Elm OSS panel discussion.
Articles and Discussion
The Keystone Testing Habit — incrementalelm.com
Dillon Kearns discusses the benefits of using TDD and unit testing in Elm.
🐮 "Is it my cow?" Elm game Postmortem - Part 3 - Animation — wiktor.toporek.me
Wiktor Toporek is back with part 3 of his blog series about the development of an Elm Game Jam game. In this post, he discusses animation.
Episode 14: The Life of a File — elm-radio.com
Dillon Kearns and Jeroen Engels revisit Evan Czaplicki's talk about organising code into files, and discuss code design and in particular, modules.
Tools and Projects
VS Code Elm extension 1.4.0 — discourse.elm-lang.org
The new version of the extension with contributions from Jon Bockhorst, Kolja Lampe and Simon Lydell has an implementation of type inference, which allows you to add inferred type annotations to functions and create function declarations from usage, among other improvements.
Elm Debug Helper: Debug.log transformation browser extension
Tomáš Látal has released Chrome and Firefox extensions for transforming Debug.log output into expandable trees in the console. Very useful! This builds on his earlier work on elm-debug-transformer.
ChristophP/elm-esm: Turn Elm compiler output into modern ES Modules
Deedo has created a tool that turns Elm compiler output into an ES6 module. dynamic-import and modulepreload are also supported.
Incremental adoption of elm-review rules
Jeroen Engels is looking for input on incremental adoption of static analysis rules in Elm projects using elm-review.
That's it for this week!
Please help me offset the costs of Elm Weekly and support my Elm work by sponsoring me on GitHub.
If you have something you’d like to submit for an upcoming edition, tweet @elmweekly with a link, send an email through to firstname.lastname@example.org, or just hit Reply.