Webpack 4.0.0 Error

[mickeyvip]

I am trying to use Webpack v4.0.0 and get the following:

ERROR in ./src/Main.elm
Module build failed: TypeError: Cannot read property 'elm' of undefined
    at Object.getOptions (/Users/me/dev/Projects/Elm/webpack4/node_modules/elm-webpack-loader/index.js:37:35)
    at Object.module.exports (/Users/me/dev/Projects/Elm/webpack4/node_modules/elm-webpack-loader/index.js:117:28)
 @ ./src/index.js 1:10-31

webpack.config.js

module.exports = {
	module: {
		rules: [
			{
				test: /\.elm$/,
				exclude: [/elm-stuff/, /node_modules/],
				use: {
					loader: 'elm-webpack-loader'
				}
			}
		],
		noParse: [/\.elm$/]
	}
};

src/index.js

const Elm = require('./Main.elm');
// import Elm from './Main.elm'
console.log('App started...');

src/Main.elm

module Main exposing (main)

import Html exposing (Html, text)


main : Html msg
main =
    text "Hello, Elm!"

[gmaugard]

I had the same error. Try to use webpack 2.2 :)

[ghost]

There's a minor error that can be bypassed to compile elm code with webpack 4. I'll make a pull request to at the very least get it to compile

[ghost]

#136

[kirisaki]

webpack 4: migration guide for plugins/loaders – webpack – Medium
https://medium.com/webpack/webpack-4-migration-guide-for-plugins-loaders-20a79b927202

Loaders should receive all options via this.query.

[mickeyvip]

@kirisaki , so the #136 should be updated to use this.query instead of this.options?

[eeue56]

We need to have continued support for older versions of webpack, too. Will changing to this.query affect that?

[mickeyvip]

So the code can look like this?

var globalOptions = this.options
    ? this.options.elm || {}
    : this.query.elm || {};

[meowgorithm]

I believe this is fixed in master, which is not yet published (see #131). Try the following in your package.json:

"elm-webpack-loader": "git://github.com/elm-community/elm-webpack-loader#7d1c6d939ea5b8b8a8f2aa2eb497e7fba49e6c71"

[ghost]

@meowgorithm - yes, as per #136, the change we discussed here has been made. I imagine the issue stays up until the new version is published, to avoid more issues about it.

[praveenperera]

@eeue56 Is there something else that needs to be done before publishing a new version to npm with #136 ?

[eeue56]

published as 4.5.0