Your solution did not work for my situation, but I did try it out on the
elm/core library, and I was able to run
elm-test and those tests passed. Really, all I had to do was symlink it into the right package directory, and sometimes delete
That solution seems to work well for packages with tests, but the packages that I’m interested in,
elm-explorations/webgl don’t have tests. In fact, one of them has an
/examples folder with applications in it.
Trying this solution, i.e. compiling with
elm make ./crate.elm will result in the error
> Map.!: given key is not an element in the map
> CallStack (from HasCallStack):
> error, called at libraries/containers/Data/Map/Internal.hs:610:17 in containers-0.5.11.0:Data.Map.Internal
Or depending on some inscrutible issues
-- INCOMPATIBLE DEPENDENCIES ------------------------------------------ elm.json
The dependencies in your elm.json are not compatible.
Essentially, the core of the problem is that I want to be able to run applications that depend on packages containing
Elm.Kernel code, which is likely to be found in a local directory, because what I’m testing is not the application, but the package.
It’s actually using applications as tests, since it’s primarily a visual inspection.