elm-janitor-apply-patches

Apply elm-janitor patches to Elm dependencies

This script can install maintenance patches from elm-janitor.

If you have questions, suggestions or problems, join the 🧹 elm-janitor channel on "Incremental Elm" discord.

This script is intended to be used until we have a nice way to apply patches integrated into elm-tooling-compiler (elmx) or maybe an alternate Elm package server can be used.

If you don't want to use this script, you can also adapt one of these solutions: pdamoc/elm-pkg-patch, robx/shelm or robinheghan/elm-git-install

Description

Like the Elm compiler, this script uses the environment variable $ELM_HOME to find the cache directory.
If it is not set, $HOME/.elm, $USERPROFILE/.elm or %appdata%\elm will be used instead.

It downloads the release archive, and then unpacks the files README.md, elm.json, LICENSE and the content of the src/ directory.
It also creates a file elm-janitor-commit.json with information about the specific downloaded commit.
If the package was already present in ELM_HOME, it is fully replaced.

During the first compilation, the Elm compiler will create the docs.json and artifacts.dat files.

Usage

There are multiple ways to apply the patches using this script.
You can clone this repository and follow the development instructions, run the script with deno, node.js or download a huge binary.

CLI params and flags

# Show the help text
elm-janitor-apply-patches --help

# Print the status which packages were patched (and with what version)
elm-janitor-apply-patches --status

# Install all patches
elm-janitor-apply-patches --all

# Install only patch for elm/parser
elm-janitor-apply-patches parser --verbose

# Install a few patches
elm-janitor-apply-patches parser json

The flag --verbose can be added to most other commands to print more information.

With the deno runtime

There are three options when you have deno installed.

1. Run the script (recommended for one-time use)

❯ deno run --allow-env=ELM_HOME,HOME --allow-read --allow-write --allow-net=github.com,codeload.github.com,api.github.com  https://raw.githubusercontent.com/elm-janitor/apply-patches/main/deno/cli.ts

2. Install the script

❯ deno install --name elm-janitor-apply-patches --allow-env=ELM_HOME,HOME --allow-read --allow-write --allow-net=github.com,codeload.github.com,api.github.com https://raw.githubusercontent.com/elm-janitor/apply-patches/main/deno/cli.ts

# And uninstall it again
❯ deno uninstall elm-janitor-apply-patches

3. Compile a huge binary that contains the deno runtime

❯ deno compile --allow-env=ELM_HOME,HOME --allow-read --allow-write --allow-net=github.com,codeload.github.com,api.github.com --output elm-janitor-apply-patches https://raw.githubusercontent.com/elm-janitor/apply-patches/main/deno/cli.ts

With node.js

The script is also published to npm.

You can run it in the node.js runtime for instance like this:

❯ npx elm-janitor-apply-patches

By downloading a binary

If stable versions should ever be created, deno compile can be used on CI to create huge release binaries.

Verifying the patch

To verify that applying the patch was successful, you can open the file elm-janitor-commit.json inside the package directory (inside ELM_HOME).

Also during runtime, every patch will print a message listing the commit id, for example:

console.info('Using elm-janitor/parser@a61f4ae instead of elm/parser@1.1.0');

You can also execute elm-janitor-apply-patches --status to receive a list of the patched packages.

Important: If you have an existing Elm project, it is best to remove the elm-stuff directory after applying the patches to ensure that the new sources are used and not old cached compiled files are used.

Development

If you don't want to patch the dependencies used for every other Elm project, you can configure $ELM_HOME to another directory.

# fish
set ELM_HOME (pwd)/elm-home
# sh
ELM_HOME=`pwd`/elm-home
# Windows CMD.exe
set ELM_HOME=%cd%\elm-home

And then let the Elm compiler download the dependencies by starting compilation.

cd example
# And run the test
elm-test-rs
# OR
elm make src/Main.elm
# and then open the generated `index.html` file
cd ..

The test will fail, because it will only print a TODO deadEndsToString string.

After that, run the script to apply the patches for elm/parser like this:

cd deno
deno run --allow-env=ELM_HOME --allow-read=../elm-home --allow-write=../elm-home --allow-net=github.com,codeload.github.com,api.github.com cli.ts --verbose parser
cd ..

Then re-run the tests or compile the example src/Main.elm file to see the output of the new deadEndsToString.

Publishing to npm

For information how to publish this deno code to npm as a node.js script, see explanation

Notes

If you rely on local documentation, you can also generate the docs.json file of an Elm package by executing elm make --docs docs.json