Update local compile server setup instructions so that code compiles

[JordanMartinez]

Fixes #220

[thomashoneyman]

Hm -- even running (set -o noglob && stack exec trypurescript 8081 $(spago sources)) still produces this when running a fresh clone of the repository and the dev server.

Note that the development instructions say to use npm run build, but this should probably say npm run build:dev.

To clarify, I don't see the issue when compiling the trypurescript executable; it's only when making the POST request to the running dev server. Loading up localhost:8080 is successfully making one POST request, but the compilation results in:

{
  "error": {
    "tag": "CompilerErrors",
    "contents": [
      {
        "suggestion": null,
        "moduleName": "Main",
        "errorLink": "https://github.com/purescript/documentation/blob/master/errors/UnknownName.md",
        "errorCode": "UnknownName",
        "message": "  Unknown module Data.Foldable\n",
        ...
      }
    ]
  }
}

I see the same result whether I'm using zsh (the default for MacOS these days) or bash, so I don't think that's the issue. If these dev instructions work fine for everyone else then perhaps this is just me and we should merge.

[JordanMartinez]

I feel like that's a separate issue we can investigate after this PR gets merged. Beforehand, we had 'ModuleNotFound' errors, so that the server wouldn't even start. Now the server starts, but isn't working correctly. Perhaps the issue is now caused by a bug in the server function or that the project's dependencies just need to be updated to match v0.14.1's dependency version?

[thomashoneyman]

Ah, I see.

I was referring to the server starting, but compilation of the code provided via the client would fail with Module Not Found errors like the one I showed above. In my shell, at least, the dev backend comes up regardless of the noglob option being set.

But I’ve seen these errors stop the server from being compiled in the first place, so we could still merge this.

It shouldn’t be a 0.14.1 issue, because the package set in the staging directory has been updated to 0.14.1.