elm-tooling
Advanced tools
Changelog
Version 1.15.0 (2023-09-30)
ℹ️ If you use macOS ARM (Apple Silicon) and have used
elm-tooling
1.11.0–1.14.1 before, you need to clear previously downloaded binaries in order to get the newest macOS ARM binary. Otherwise you’ll keep using the one from 1.11.0.# Remove downloaded binaries: rm -R ~/.elm/elm-tooling/elm/0.19.1/ # Install new binaries: cd your-project npx elm-tooling install
The previous macOS ARM binary could sometimes segfault while installing Elm packages. This was fixed by Evan upgrading the Elm compiler to a newer GHC version. He then uploaded a macOS ARM binary to official Elm 0.19.1 release. This version of elm-tooling
downloads a copy of that binary.
Changelog
Version 1.14.1 (2023-09-09)
export default
, but apparently export =
is the correct syntax to use for packages that export a single function, which can be used both in CJS and MJS. (Read more about Incorrect default export). It should now be possible to do const elmToolingCli = require("elm-tooling")
in a @ts-checked
ed JS file without TypeScript complaining.Changelog
Version 1.13.0 (2023-03-02) – deprecated
Note: This version has been deprecated, since it contains a broken elm-format 0.8.6 Windows binary link. Use 1.13.1 or later instead.
Changelog
Version 1.12.0 (2023-01-16)
ℹ️ If you use macOS ARM (Apple Silicon) and have used
elm-tooling
1.11.0 before, you need to clear previously downloaded binaries in order to get the newest macOS ARM binary. Otherwise you’ll keep using the one from 1.11.0.# Remove downloaded binaries: rm -R ~/.elm/elm-tooling/elm/0.19.1/ # Install new binaries: cd your-project npx elm-tooling install
Why replace the ARM 64 binaries? The ones in this release are compiled from the same commit as the official x86_64 binaries. The ones in 1.11.0 were compiled from a later commit.
The ones in 1.11.0 still work, but can result in surprises. There are some unreleased Elm compiler commits that result in ever so slightly different compiled JavaScript. Many build systems hash outputs for cache busting. If you run a binary compiled from a later commit locally but an official one on a build server, you might be confused why you get different hashes locally and on the build server for example. There’s also a risk that something compiles on your local computer, but not on the build server, or someone else’s computer (who doesn’t use ARM 64).
Thanks to Mario Rogic for compiling the binaries!
Changelog
Version 1.11.0 (2023-01-08)
ℹ️ If you use macOS ARM (Apple Silicon) and have used
elm-tooling
before, you need to clear previously downloaded binaries in order to get macOS ARM binaries. Otherwise you’ll keep using Rosetta.# Remove downloaded binaries: rm -R ~/.elm/elm-tooling/ # Install new binaries: cd your-project npx elm-tooling install
Similarly, if you have tried
elm-tooling
on Linux ARM before, you also need to clear previously downloaded, non-working x86_64 binaries.
elm-tooling
can now be run on any platform. (Previously it exited early on unsupported platforms.)elm-tooling install
prints a message for tools that have no binary for the current platform. (It does not fail the command.)