Skip to content

Invalid configuration object: mangleExports using 5.0.0-beta.14 #1677

@JAicewizard

Description

@JAicewizard

Bug report

What is the current behavior?
When I use the example configuration for mangleExports:

Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.optimization has an unknown property 'mangleExports'. These properties are valid:
   object { checkWasmTypes?, chunkIds?, concatenateModules?, flagIncludedChunks?, hashedModuleIds?, mangleWasmImports?, mergeDuplicateChunks?, minimize?, minimizer?, moduleIds?, namedChunks?, namedModules?, noEmitOnErrors?, nodeEnv?, occurrenceOrder?, portableRecords?, providedExports?, removeAvailableModules?, removeEmptyChunks?, runtimeChunk?, sideEffects?, splitChunks?, usedExports? }
   -> Enables/Disables integrated optimizations

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

create webpack.config.js as example profided in documentation:

module.exports = {
  //...
  optimization: {
    mangleExports: false
  }
};

What is the expected behavior?
Webpack should not mangle exports like the documentation provides

Other relevant information:
webpack version: 5.0.0-beta-14
Node.js version: v13.12.0
Operating System: linux
Additional tools: [email protected]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions