Skip to content

EvalSourceMapDevToolPlugin filename option is ignored #3890

@logicbomb421

Description

@logicbomb421

Bug report

What is the current behavior?

I am attempting to use webpack.EvalSourceMapDevToolPlugin with the filename option (per the docs) to generate standalone source maps for a build artifact tool, but it appears the filename option is ignored, and all source maps are inlined with the generated bundles.

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

Create a simple webpack.config.js that uses webpack.EvalSourceMapDevToolPlugin with { filename: '[name].js.map' } as the options object. Run webpack, and examine the output files. Notice there are no *.js.map files generated.

Conversely, the same config using webpack.SourceMapDevToolPlugin does produce standalone .js.map files.

What is the expected behavior?

The filename option is not ignored in webpack.EvalSourceMapDevToolPlugin, and standalone source maps are generated.

Other relevant information:
webpack version: 4.39.0
Node.js version: 10.14.2
Operating System: macOS 10.15.4
Additional tools: N/A

Please let me know if I can provide any additional information. Thanks!

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