Bug report
What is the current behavior?
I'm getting an error when using the ProfilingPlugin. I get an error reporting that n.args.data.frames is not iterable when dropping the events.json into Chrome.
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.
The attached file gives me this experience: events.json.zip
These are the same steps defined in #11780 where @leimonio reported the same problem.
What is the expected behavior?
Chrome should render the profiler as per the instructions in the Usage: https://webpack.js.org/plugins/profiling-plugin/#usage-custom-outputpath
Other relevant information:
webpack version: 5.83.1
Node.js version: v16.19.0
Operating System: MacOSX
Additional tools:
Chrome version Version 113.0.5672.92
Bug report
What is the current behavior?
I'm getting an error when using the ProfilingPlugin. I get an error reporting that
n.args.data.frames is not iterablewhen dropping the events.json into Chrome.If the current behavior is a bug, please provide the steps to reproduce.
The attached file gives me this experience: events.json.zip
These are the same steps defined in #11780 where @leimonio reported the same problem.
What is the expected behavior?
Chrome should render the profiler as per the instructions in the Usage: https://webpack.js.org/plugins/profiling-plugin/#usage-custom-outputpath
Other relevant information:
webpack version: 5.83.1
Node.js version: v16.19.0
Operating System: MacOSX
Additional tools:
Chrome version Version 113.0.5672.92