Skip to content
This repository has been archived by the owner on Feb 7, 2022. It is now read-only.

name/output.filename should not be required #92

Open
mzealey opened this issue Jan 10, 2019 · 1 comment
Open

name/output.filename should not be required #92

mzealey opened this issue Jan 10, 2019 · 1 comment

Comments

@mzealey
Copy link

mzealey commented Jan 10, 2019

Explain the problem

name or output.filename parameters are required

Expected Behaviour

With webpack 4 at least these were not present in my config prior to installing parallel-webpack (the output directories were different as I have different build versions for different platforms)

Actual Behaviour

Dies in webpackWorker.js : getAppName due to parameter not existing.

@npetkov
Copy link

npetkov commented Jan 7, 2020

I think the issue is caused by getAppName expecting a configuration object.

function getAppName(webpackConfig) {
    var appName = webpackConfig.name || webpackConfig.output.filename;
...

Exporting functions instead of configuration objects is obviously a no-go.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants