Problem with initial file compilation on Windows about elm-brunch

[madsflensted]

I don't have a platform to reproduce this error - but I suspect it relates to the "mainModules" setting - and that elm-brunch does not recognize the main module due to the non-windows path spec. All non-main modules are skipped on first alert from brunch - since brunch at startup will send events for all files.

maybe you can try to change brunch config to:

   mainModules: ["web\\static\\elm\\Chat.elm"]

and see what that does?

You could also run brunc with --debug and see if files are detected and processed.

[rudolfb]

Hi Mads,

Sorry for the late reply. Easter belonged to my daughter.

Changed the brunch-config.js to

    elmBrunch: {
      mainModules: ["web\\static\\elm\\Chat.elm"]
    }

and the chat.js file is now automatically created on running

mix phoenix.server

So this seems to resolve my problem on Windows. Thanks. Now I just need to see if this works on Linux and Mac.

Regards

Rudolf

[rudolfb]

Hi Mads,

Ok, tested on Linux, and changing the path to

    elmBrunch: {
      mainModules: ["web\\static\\elm\\Chat.elm"]
    }

failed to compile the Chat.elm to chat.js. Is this something you would have to implement in elm-brunch, to convert the path seperators from / to \\ on Windows?

Regards

Rudolf

[madsflensted]

Ok, Good to hear.

The whole plugin is due for an overhaul based on the new plugin structure
brunch uses, so a general fix for this Windows / Linux path issue would go
with that release.
On Mar 29, 2016 17:26, "Rudolf Bargholz" [email protected] wrote:

Hi Mads,

Ok, tested on Linux, and changing the path to

elmBrunch: {
  mainModules: ["web\\static\\elm\\Chat.elm"]
}

failed to compile the Chat.elm to chat.js. Is this something you
would have to implement in elm-brunch, to convert the path seperators from
/ to \ on Windows?

Regards

Rudolf

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#16 (comment)