extract-css-chunks-webpack-plugin: Throws when compiling (recording phase): "Path variable [name] not implemented in this context"

I am watching this PR, too 😃

yea, you need to provide the options still. react-loadable’s latest babel plugin replaces the need for all that.

…truth is, another plugin that does what dual-import does and what react-loadable’s babel plugin does is coming out any day now:

https://github.com/faceyspacey/babel-plugin-universal-import

and a few other things. FYI, if you get what you have working, the transition will be seamless.

…dont try to use that plugin. it requires the @next dist-tag of react-universal-component. u could, but i gotta revisit before i launch. it’s been sitting on the vine for a while. there’s actually a PR to webpack i’m working on pushing through to make dynamic imports work universally. things are about to come together nicely.

Regarding these missing chunk names/ids: I figure it would be useful to throw instead of producing a breaking build.

function getPath(compilation, source, chunk) {
	return function(format) {
		if (chunk.name == null && chunk.id == null) {
			throw new Error("Missing chunk id/name! Can't proceed without. Please check your setup of babel-plugin-dual-import and be sure to prevent comments from being removed in your transpiled code!")
		}
		return compilation.getPath(format, {
			chunk: chunk
		}).replace(/\[(?:(\w+):)?contenthash(?::([a-z]+\d*))?(?::(\d+))?\]/ig, function() {
			return loaderUtils.getHashDigest(source, arguments[1], arguments[2], parseInt(arguments[3], 10));
		});
	}
}

Pseudo pull-request 😉

…if you’re using a babel feature to strip comments, you will have this issue, as it will remove the magic comment:

https://github.com/faceyspacey/babel-plugin-dual-import/issues/1#issuecomment-313891179

That could be it.