`output` option not passing down to the elm-make

Using elm-webpack-loader 4.1.1 (from package.json), webpack 1.14.0

Maybe I am using the tool wrong, but it seems that the output option in the loader is not properly transmitting the information to elm-make - it appends to a temp filename generated elsewhere.

I have the following line in the webpack.config.js file:

...
module: {
  loaders: [
    ...
    {
        test:    /\.elm$/,
        exclude: [/elm-stuff/, /node_modules/],
        loader:  'elm-webpack?output=/tmp/elm.js',
      },
    ...

And when I run webpack, I get the following message:

ERROR in ./src/Main.elm
Module build failed: Error: Compiler process exited with error ENOENT: no such file or directory, open '/tmp/11707-20012-fp4rvi.9ggr9newmi/tmp/elm.js'

I tried to change this option because when running in a docker container, it kept generating these temp files in my current directory. Is there a misconfiguration from my side? Is it reading something from an environment variable (which would explain the docker weirdness). Sorry if I missed the doc on this.

Thank you in advance for any help

[baudren]

I am running my application through a bunch of docker files, with docker-compose. The front-end is running with webpack-dev-server.

If I start locally the application, the temp file goes to /tmp/[cryptic-numbers].js, which is fine. However, when run from the docker container, the temp file goes to the current workdir.

Therefore, at each new compilation, I have a new cryptic javascript file in the root directory of my current project. Adding this to .gitignore with some regex matching could work, but what would be really nice is to have them generated elsewhere.

Hope that makes sense!

[teesloane]

Also running into this exact issue; did you have any luck solving this @baudren?

Thanks!