Upgrade to Elm 0.19

[accordeiro]

Hi! I'm not sure if this is already being done by someone, but if not I'd love to help upgrading create-elm-app to Elm 0.19 – just let me know. :)

[halfzebra]

@xtian have initiated the work on the upgrade.

You are very welcome to join the conversation in #256 if you'd like to help!

[berry]

Just curious. I am using create-elm-app. It helps me a lot in building a JS-Elm-hybrid web-app. I want to port this app to 0.19. Any idea when create-elm-app will support 0.19? Thanks very much in advance.

[halfzebra]

Update on 0.19 support

Create Elm App upgrade will be possible when it's dependencies are upgraded to 0.19

The work is being done in:

• Update for Elm 0.19 elm-community/elm-webpack-loader#142
• Support Elm 0.19 NoRedInk/find-elm-dependencies#8
• Update for 0.19 rtfeldman/node-elm-compiler#72

All of these projects are maintained by the community, so anyone is welcome to help.

Stay tuned! CEA with 0.19 is coming 🙂

[optikfluffel]

All three of them are merged and released now. 😁

[halfzebra]

Waiting for xtian#1, I think the next major release for Create lm App is happening this weekend.

[halfzebra]

Create Elm App with Elm 0.19 and Webpack 4 is available at npm install create-elm-app@next

Please let me know if you'll experience any issues!

I'll be preparing the release(#272) according to the plan.

[optikfluffel]

I get some fsevents related errors when trying to install using npm install create-elm-app@next -g on the macOS 10.14 Public Beta:

npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
/usr/local/bin/elm-app -> /usr/local/lib/node_modules/create-elm-app/bin/elm-app-cli.js
/usr/local/bin/create-elm-app -> /usr/local/lib/node_modules/create-elm-app/bin/create-elm-app-cli.js

> fsevents@1.1.2 install /usr/local/lib/node_modules/create-elm-app/node_modules/elm-test/node_modules/fsevents
> node install

node-pre-gyp ERR! Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.2/fse-v1.1.2-node-v64-darwin-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for fsevents@1.1.2 and node@10.9.0 (node-v64 ABI) (falling back to source compile with node-gyp)
node-pre-gyp ERR! Tried to download(undefined): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.2/fse-v1.1.2-node-v64-darwin-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for fsevents@1.1.2 and node@10.9.0 (node-v64 ABI) (falling back to source compile with node-gyp)
  SOLINK_MODULE(target) Release/.node
  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
  CXX(target) Release/obj.target/fse/fsevents.o
In file included from ../fsevents.cc:85:
../src/methods.cc:14:12: warning: 'Call' is deprecated [-Wdeprecated-declarations]
  handler->Call(3, argv);
           ^
../../../../nan/nan.h:1646:3: note: 'Call' has been explicitly marked deprecated here
  NAN_DEPRECATED inline v8::Local<v8::Value>
  ^
../../../../nan/nan.h:102:40: note: expanded from macro 'NAN_DEPRECATED'
# define NAN_DEPRECATED __attribute__((deprecated))
                                       ^
In file included from ../fsevents.cc:85:
../src/methods.cc:14:12: warning: 'Call' is deprecated [-Wdeprecated-declarations]
  handler->Call(3, argv);
           ^
../../../../nan/nan.h:1646:3: note: 'Call' has been explicitly marked deprecated here
  NAN_DEPRECATED inline v8::Local<v8::Value>
  ^
../../../../nan/nan.h:102:40: note: expanded from macro 'NAN_DEPRECATED'
# define NAN_DEPRECATED __attribute__((deprecated))
                                       ^
1 warning generated.
1 warning generated.
rm: ./Release/.deps/Release/obj.target/fse/fsevents.o.d.raw: No such file or directory
make: *** [Release/obj.target/fse/fsevents.o] Error 1
  SOLINK_MODULE(target) Release/fse.node
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:239:12)
gyp ERR! System Darwin 18.0.0
gyp ERR! command "/usr/local/Cellar/node/10.9.0/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/usr/local/lib/node_modules/create-elm-app/node_modules/elm-test/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node" "--module_name=fse" "--module_path=/usr/local/lib/node_modules/create-elm-app/node_modules/elm-test/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64"
gyp ERR! cwd /usr/local/lib/node_modules/create-elm-app/node_modules/elm-test/node_modules/fsevents
gyp ERR! node -v v10.9.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/Cellar/node/10.9.0/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/usr/local/lib/node_modules/create-elm-app/node_modules/elm-test/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node --module_name=fse --module_path=/usr/local/lib/node_modules/create-elm-app/node_modules/elm-test/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/create-elm-app/node_modules/elm-test/node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:961:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:250:5)
node-pre-gyp ERR! System Darwin 18.0.0
node-pre-gyp ERR! command "/usr/local/Cellar/node/10.9.0/bin/node" "/usr/local/lib/node_modules/create-elm-app/node_modules/elm-test/node_modules/fsevents/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /usr/local/lib/node_modules/create-elm-app/node_modules/elm-test/node_modules/fsevents
node-pre-gyp ERR! node -v v10.9.0
node-pre-gyp ERR! node-pre-gyp -v v0.6.36
node-pre-gyp ERR! not ok
Failed to execute '/usr/local/Cellar/node/10.9.0/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/usr/local/lib/node_modules/create-elm-app/node_modules/elm-test/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node --module_name=fse --module_path=/usr/local/lib/node_modules/create-elm-app/node_modules/elm-test/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64' (1)
  COPY /usr/local/lib/node_modules/create-elm-app/node_modules/elm-test/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
  TOUCH Release/obj.target/action_after_build.stamp
npm WARN ajv-keywords@3.2.0 requires a peer of ajv@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.1.2 (node_modules/create-elm-app/node_modules/elm-test/node_modules/fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.1.2 install: `node install`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

+ create-elm-app@2.0.0-rc2
updated 1 package in 55.713s

[halfzebra]

@accordeiro thanks for the feedback! It's a known issue with fsevents/fsevents#229, we just need to raise the awareness in rtfeldman/node-test-runner#264 to get this fixed.

Which version of node are you running?

[optikfluffel]

@halfzebra I'm running v10.9.0, when I use v9.11.2 it seems to work.

[odoe]

I'm getting an odd error about corrupt binary on Mac OS 10.13.6
node and npm installed via nvm if that matters.
node: 10.9.0
npm: 6.2.0

create-elm-app test-app

Creating test-app project...

Success! Compiled 1 module.
-- CORRUPT BINARY - /Users/<user>/.elm/0.19.0/package/elm/browser/1.0.0/objs.dat

The binary data at
/Users/<user>/.elm/0.19.0/package/elm/browser/1.0.0/objs.dat is corrupt.

I have Elm 0.19.0 installed via the Mac installer.

Thanks!

[kwonoh]

@odoe
I had the same error message.
The error message is disappeared by deleting the ~/.elm and <project>/elm-stuff directories and rebuild the project by elm-app build.
Surprisingly, once I did this, creating a new project did not give me the error message.

[mbylstra]

@kwonoh's fix worked for me (thanks!). I also find that after doing this creating a new project does not give the error message. However, if I then remove ~/.elm and create a new project, I get the CORRUPT BINARY error message again.

[jtrunick]

I'm continually getting this for anything i click on or do in my app:
RangeError: Maximum call stack size exceeded
Doing a build, the app works as expected.

[berry]

Hi, I installed npm install create-elm-app@next. Should Hot Module Replacement (HMR) work? Because, on my Macbook (Safari and Firefox) it does not work. Only after a browser refresh code changes are visible.