Package Details: elm-platform 0.19.0-1

Git Clone URL: (read-only)
Package Base: elm-platform
Description: Bundle of all core development tools for the Elm language.
Upstream URL:
Keywords: elm language programming
Licenses: BSD3
Conflicts: elm-platform-bin, nodejs-elm
Submitter: Luchs
Maintainer: Luchs
Last Packager: Luchs
Votes: 16
Popularity: 0.186917
First Submitted: 2015-11-20 13:48
Last Updated: 2018-08-21 18:55

Latest Comments

1 2 3 4 Next › Last »

Luchs commented on 2018-08-21 18:58

Thanks for the notification, I updated the package. I hope it builds fine for everyone :)

As always, I also uploaded the binary package to

aptinio commented on 2018-08-21 16:20

First of all, thanks for maintaining this!

Elm 0.19.0 just came out.

Luchs commented on 2018-07-11 19:22

Thanks, I updated the PKGBUILD with your suggestions.

pfrenssen commented on 2018-07-11 07:48

I really like the solution of @cippaciong to build in a local directory, and it also fixes the other problems reported here. However it wasn't creating the build folder in the right location for me and the symlink to it was broken. I fixed it by providing an absolute path to the build folder.

cippaciong commented on 2018-06-25 14:27

@Luchs: I adjusted the PKGBUILD in order to build ghc and elm in a clean, local .stack directory that is deleted at the end of each build. If you wanna check it out you can find it here

cippaciong commented on 2018-06-21 13:00

Hello, in the end I was able to build elm-platform along with stack-static 1.7.1-1 in a clean environment (Docker container). The steps to reproduce it should be:

  1. Fix the soft link as suggested by @wolfjb
  2. remove --install-ghc flag from stack build (not sure if necessary)
  3. rm -r $HOME/.stack
  4. makepkg

After the build I ran elm-repl inside the container with a minimal set of packages installed and noticed that nodejs seems to be a runtime dependency:

The REPL relies on node.js to execute JavaScript code outside the browser.I could not find executable 'node' or 'nodejs' on your computer though!

I think that nodejs should be added as a dependency or at least as an optional dependency.

Hope this helps :)

ptrxyz commented on 2018-06-11 12:00

It seems this package conflicts with 'elm-platform-bin'. Could you please add this to the PKGBUILD?

wolfjb commented on 2018-06-08 19:13

The elm-compiler zip file expands as compiler-0.18.0, so line 30 in the PKGBUILD needs be:

ln -sf compiler-${pkgver} elm-compiler

But now I get a link error: /usr/bin/ld: final link failed: Nonrepresentable section on output

Luchs commented on 2018-06-07 22:19

I fixed the elm-compiler hash, which makes it build again with my old stack version (stack-static 1.5.1-1). I currently don't have time to try/fix building with newer stack versions, sorry. Patches welcome, of course.

If you have trouble building this, consider using a binary package: either the official one from NPM, or binary versions of this package by me linked in the comments below.

shevket commented on 2018-05-30 01:56

I had a checksum error for elm-compiler just like daenney, indeed resolved by changing its checksum with 911109bbedf13c5a5c154ff8b60087b43cfd8be5e165df09b4e8f532a9f22fcd but now after this I get the following error in build():

/home/AUR/elm-platform/src/elm-compiler/: getDirectoryContents:openDirStream: does not exist (No such file or directory)

[edit/side note]: building works after finally installing nvm and npm i -g elm