create-elm-app
create-elm-app copied to clipboard
elm-app start fails when Emacs creates lock file
Is this a bug report?
Yes
Environment
-
node -v
:v10.20.1
-
npm -v
:6.11.3
-
npm ls create-elm-app -g
(if you havenβt ejected):
/home/pierre/.local/share/npm/lib
βββ [email protected]
- Operating system: Linux 5.5.0-2-amd64 #1 SMP Debian 5.5.17-1 (2020-04-15) x86_64 GNU/Linux
Steps to Reproduce
-
elm-app start
- modify Elm file with Emacs without saving
Expected Behavior
Nothing should happen as the actual Elm file has not been modified.
Actual Behavior
elm-app stops with the following error:
/home/pierre/.local/share/npm/lib/node_modules/create-elm-app/scripts/start.js:11
throw err;
^
Error: ENOENT: no such file or directory, stat '/home/pierre/Development/elm-lambda-playground/src/Lambda/.#Parser.elm
(Emacs's lockfile is a symlink pointing to a non-existant filename)
Reproducible Demo
https://github.com/kephas/elm-lambda-playground
I'm having the same issue. Temporarily switching to vscode.
I configured Emacs to stop creating the lock files.
ReactJS's server fails the same way if encounters an Emacs lock file.
As @kephas suggested, you can tell Emacs to avoid creating lock files for your Elm project. Here's how: https://stackoverflow.com/a/62571200/73603