Bug report
What is the current behavior?
JSON produced by ProfilingPlugin is shown in Chrome with one single "Evaluate Script" line without any additional info.
Although events.json is pretty large, contains a lot of lines, timestamps, and looks like a valid JSON file.
Maybe there are some changes in Chromium itself related to this issue.

If the current behavior is a bug, please provide the steps to reproduce.
- Create new project with
npx create-react-app test-project.
- Eject (
cd test-project && npm run eject)
- Add
new webpack.debug.ProfilingPlugin() to plugins section at config/webpack.config.js
- Start dev server with
npm start then shutdown it (or just npm run build).
- Drag and drop generated events.json into the Chrome DevTools Profiler.
Or just unarchive and use attached events.json
P.S. I can reproduce issue in all my projects, with different configs, and none of them uses CRA. It's just easy-to-check example with wide used and probably well tested config.
What is the expected behavior?
I exepect to see some additional info, eg timings for each used plugin, "Bottom-up" list, etc.
Other relevant information:
webpack version: 4.42.0
Node.js version: v14.10.1
Operating System: macOS Catalina 10.15.7
Additional tools: Google Chrome 86.0.4240.80 (Official Build) (x86_64)
Bug report
What is the current behavior?

JSON produced by ProfilingPlugin is shown in Chrome with one single "Evaluate Script" line without any additional info.
Although events.json is pretty large, contains a lot of lines, timestamps, and looks like a valid JSON file.
Maybe there are some changes in Chromium itself related to this issue.
If the current behavior is a bug, please provide the steps to reproduce.
npx create-react-app test-project.cd test-project && npm run eject)new webpack.debug.ProfilingPlugin()to plugins section at config/webpack.config.jsnpm startthen shutdown it (or justnpm run build).Or just unarchive and use attached events.json
P.S. I can reproduce issue in all my projects, with different configs, and none of them uses CRA. It's just easy-to-check example with wide used and probably well tested config.
What is the expected behavior?
I exepect to see some additional info, eg timings for each used plugin, "Bottom-up" list, etc.
Other relevant information:
webpack version: 4.42.0
Node.js version: v14.10.1
Operating System: macOS Catalina 10.15.7
Additional tools: Google Chrome 86.0.4240.80 (Official Build) (x86_64)