Webpack.js.org: Passing ecmaVersion results in "Invalid configuration object"

Created on 28 Sep 2020  路  6Comments  路  Source: webpack/webpack.js.org

Bug report




What is the current behavior?

v4.44.2 crashes with "Invalid configuration object" telling me that output.ecmaVersion is not a valid option

If the current behavior is a bug, please provide the steps to reproduce.

Provide output.ecmaVersion of any value. Tested: 5 and 6

What is the expected behavior?

No crash on using documented option https://webpack.js.org/configuration/output/#outputecmaversion

Other relevant information:
webpack version: 4.44.2
Node.js version: 12.13.0
Operating System: Windows 7
Additional tools:

Most helpful comment

I want to work on this issue.

All 6 comments

This option for webpack@5 and it was removed

The docs for that setting specifically mention Webpack 4, so it would be good to edit the docs in that case.

The default value of output.ecmaVersion in webpack 4 is 5

I want to work on this issue.

/cc @webpack/documentation-team high priority

@evilebottnawi
https://github.com/webpack/webpack.js.org/pull/4017
Have raised a PR for the documentation

This issue can be merged into #3968

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Pixelatex picture Pixelatex  路  19Comments

dmitriid picture dmitriid  路  20Comments

TheLarkInn picture TheLarkInn  路  23Comments

estaub picture estaub  路  56Comments

simon04 picture simon04  路  17Comments