Specify main modules for elm make

If my understanding is correct it’s currently necessary to specify all main modules that will be using ports to elm-make. For example:

elm-make Components/ComponentA/Main.elm Components/ComponentB/Main.elm

If left unspecified, it will result in an build error that says there cannot be multiple main modules. Something like this:

This module has ports, but ports can only appear in the main module.

89│ port tasks : Signal (Task Never ())
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Ports in library code would create hidden dependencies where importing a module
could bring in constraints not captured in the public API. Furthermore, if the
module is imported twice, do we send values out the port twice?

I’m not sure what the appropriate solution is. Considering you specify the path to a single Main module via require.

require('Components/ComponentA/Main.elm')
require('Components/ComponentB/Main.elm')

It would seem that if you did this you’d output the entire Elm core run-time with each component.

[eeue56]

Implemented and released as part of 4.4.0. elm-webpack-loader will be maintained after 0.19.

See here for how to use it: https://github.com/elm-community/elm-webpack-loader#files-default---path-to-required-file

[dynajoe]

I believe both projects will likely be obsolete after the upcoming 0.19 release. I’m glad the project works for you!