`webpack --profile` outputs invalid JSON when ENV not set

[timhwang21]

Hi, I am not sure this repository is the correct place to file this issue, if it's not I would appreciate being pointed in the right direction. Thanks!

Do you want to request a feature or report a bug?
Bug / BUX

What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce.
When running webpack --profile and ENV isn't set, the string WARN: webpack env is not set, assuming local is appended to the top of the outputted stats.json. This leads to the JSON being invalid, which while easy to manually fix, is annoying. For example this affects things like the Webpack bundle analyzer plugin.

If invalid JSON is intended to ensure the user checks it out, please close this issue 😀

What is the expected behavior?
Valid JSON is outputted.

If this is a feature request, what is motivation or use case for changing the behavior?
Maybe the warning could be output in the command line instead of in the file.

Please mention other relevant information such as the browser version, Node.js version, Operating System and programming language.

[evenstensberg]

Hey @timhwang21 , let me investigate and get back to you!

[itsMapleLeaf]

@timhwang21 I can't reproduce this in v3 or v4. Could you create a repo to illustrate the issue? Also include the webpack version you're using.

[ematipico]

@timhwang21 are there any updates on this? Unfortunately I can't reproduce the issue

[timhwang21]

Hi, unfortunately I haven't had time to look into this, and probably won't for the near future. I encountered this when profiling a large application whose build process is a mix of gulp and various webpack versions, so its very likely the problem is on my end.

Thanks!