Incompatible with 0.19.1

[jxxcarlson]

Hi, the elm-desktop-app run command will not work if the installed version of Elm is 0.19.1.

I did try replacing every occurrence of 0.19.9 in node-modules with 0.19.1, but got the same error as before:

data['elm-version'] should be equal to one of the allowed values

(( Great package! ))

PS. Got the current version working by doing

$ npm i --save-dev [email protected]
$ npx elm-desktop-app run

[objarni]

Any progress on this April issue? Got into it too using the official instructions, and the workaround didn't help me.

olof@ripley:~/my-app$ elm --version
0.19.1
olof@ripley:~/my-app$ elm-desktop-app run
/home/olof/my-app/elm-stuff/elm-desktop-app/app /home/olof/my-app
/home/olof/my-app
data['elm-version'] should be equal to one of the allowed values

[objarni]

This is the output of (re)installing elm-desktop-app:

olof@ripley:~/my-app$ npm install -g elm-desktop-app
/home/olof/.npm-global/bin/elm-desktop-app -> /home/olof/.npm-global/lib/node_modules/elm-desktop-app/cli.js
+ [email protected]
updated 1 package in 4.228s

[objarni]

And this is the content of elm.json:

olof@ripley:~/my-app$ cat elm.json 
{
    "type": "application",
    "source-directories": [
        "src"
    ],
    "elm-version": "0.19.1",
    "dependencies": {
        "direct": {
            "elm/browser": "1.0.2",
            "elm/core": "1.0.5",
            "elm/html": "1.0.0",
            "elm/json": "1.1.3"
        },
        "indirect": {
            "elm/time": "1.0.0",
            "elm/url": "1.0.0",
            "elm/virtual-dom": "1.0.2"
        }
    },
    "test-dependencies": {
        "direct": {},
        "indirect": {}
    },
    "elm-desktop-app": {
        "name": "pump-bishop-sigma",
        "app-id": "net.avh4.elm-desktop-app.replace-this-with-your-own-app-id.pump-bishop-sigma"
    }
}

[objarni]

Oh, I checked the installed config.schema.json in node_modules, and it only mentioned elm0.19.0. I tried adding elm0.19.1 there but still not working.

Is the elm-desktop-app with 0.19.1 compatibility maybe not published yet?

[objarni]

OK, I got the workaround working. Problem was that npm init hadn't been run i directory before. I hope these comments can help in some way in getting this great idea more production ready! @avh4 The workaround assumes npm init before npm i --save-dev [email protected].