Compiled script not being served from http://localhost:8080/static/js/main.js about elm-webpack-starter HOT 11 CLOSED

"The system cannot find the path specified." <-- Something is off if you're seeing it; since your install fails, running npm start is bound to not work. Unfortunately I have no access to a Windows machine, but it could be also due to you changing any path info.

The reinstall script performs a number of commands in sequence. To start troubleshooting, it would be good to know at which step exactly are you failing. Try doing these one task at a time:

npm i rimraf 
rimraf node_modules
npm uninstall -g elm
npm i -g elm 
npm i 
elm package install

It's worth noting that the project structure changed (see the Changelog), so you should adapt your project to the latest folder structure (preferably), or vice versa. As another option, I'd try cloning and building a fresh elm-webpack-starter repo and, assuming it works, move your project over bit by bit..

from elm-webpack-starter.

Thank you for helping me out it is very much appreciated.

I decided to trying to get everything to install properly in an "empty" starter folder downloaded from the master branch. Which isn't working

npm i rimraf
rimraf node_modules
npm uninstall -g elm
npm i -g elm

all ran without error, just a few warning. you can see them in attached file.

npm i

I got these warnings
`-- UNMET PEER DEPENDENCY [email protected]

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN [email protected] requires a peer of elm-webpack-loader@^4.1.1 but none was installed.

I tried manually installing
npm i elm-webpack-loader@^4.1.1
Which gave me these warnings

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

So I tried npm i elm-webpack-loader
which gave me these warnings
`-- UNMET PEER DEPENDENCY [email protected]

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN [email protected] requires a peer of elm-webpack-loader@^4.1.1 but none was installed.

Then I tried npm i [email protected]

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN [email protected] requires a peer of elm-webpack-loader@^4.1.1 but none was installed.

I am at loss as to what to try next.

install log.txt

from elm-webpack-starter.

I tried manually installing each of the packages in the package.json file.

They all gave me the warning
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

See attached
package manual install.txt

from elm-webpack-starter.

Hmm, not getting other reports of this. How about trying updating your version of Node? I'm running 6.0

from elm-webpack-starter.

I already updated my version of node. I am running version v6.9.4.

from elm-webpack-starter.

+1 i'm just gonna revert to 0.8.0
I've just noticed Main.elm doesn't have module Main..

from elm-webpack-starter.

+1. Reverting to the 0.8.0 version of webpack.config.js got it going again. Maybe related to running on Windows?

from elm-webpack-starter.

I tried reverting to 0.8.0 version but it didn't work either. I guess it just doesn't work well either on Windows or on my setup. Thank you all for being helpful.

from elm-webpack-starter.

I pushed a newer version yesterday, with updated packages. Perhaps give that a try, do a clean clone and install. Seemed to work fine, but that's on my Mac. Sorry I can't be of more help.

from elm-webpack-starter.

@JonathanDDuncan does you try resolve?
https://webpack.github.io/docs/troubleshooting.html#windows-paths

from elm-webpack-starter.

I had the same issue and created a pull request that makes webpack's config work on Windows machines.

#45

from elm-webpack-starter.