webpack-dashboard: `Could not load module/asset sizes.` after upgrade from 0.4.0 -> 1.0.0-3
Please provide a description of the bug / issue, and provide the details below: Getting an error after upgrading webpack-dashboard
Could not load module/asset sizes.
Error: Cannot read property 'length' of undefined Could not analyze bundle problems. undefined
====================================================================
If the issue is visual, please provide screenshots here
Steps to reproduce the problem
Just starting up dashboard causes the issue - code compiles fine, but modules, assets, and problems windows do not render any info
Please provide a gist of relevant files
- My start.sh command:
./node_modules/.bin/webpack-dashboard -- \
./node_modules/.bin/webpack-dev-server \
--config webpack/webpack.config.js \
--port 3000 \
--host [redacted] \
--history-api-fallback \
--content-base ./src \
--open \
--inline \
--hot \
--debug
- webpack.config.js
devServer: {
clientLogLevel: 'none',
disableHostCheck: true,
noInfo: true,
quiet: true,
stats: 'errors-only',
},
plugins: [
//...
new DashboardPlugin(),
]
====================================================================
More Details
- What operating system are you on? OSX
- What terminal application are you using? iTerm2
- What version of webpack-dashboard are you using? 1.0.0-3
- What is the output of running
echo $TERM? xterm-256color - webpack v3.5.5
- webpack-dev-server v2.7.1
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 13
- Comments: 44 (16 by maintainers)
Commits related to this issue
- Bug: Fix bad sourcemaps parsing. (#44) In working through FormidableLabs/webpack-dashboard#182 at a minimum, we have a bug where `inspectpack` removes all lines _after_ a `sourceMappingUrl` comment, ... — committed to FormidableLabs/inspectpack by ryan-roemer 7 years ago
- Add actual logging / better error capture in worker. See FormidableLabs/webpack-dashboard#182 — committed to FormidableLabs/inspectpack by ryan-roemer 7 years ago
@jpduckwo Thanks. That error is resolved after upgrading to 1.0.0-7. But getting new error. Any leads to solve this?
@ryansully –
inspectpack@1.3.2is the correct, most up to date version, and withinwebpack-dashboard’s semver range inpackage.json.@tptee @kenwheeler – We could bump
package.jsonfrom"inspectpack": "^1.3.0",to"inspectpack": "^1.3.2",and we should updateyarn.lock+package-lock.jsonfiles…Side note – we should get a procedure for maybe PRs to ensure both
yarn.lock+package-lock.jsonare regenerated. Currently they have different versions ofinspectpackand thepackage-lock.jsonfile doesn’t even meet semver requirements.I’m having an issue after upgrading too. I’ve tried adding pathinfo: true, my inspectpack is 1.3.2… any ideas?
Dashboard Log window shows this at the start the repeats with ‘could not analyze bundle problems.’
@jpduckwo / everyone else – I’m closing this issue since we’ve solved what originally opened it. Please open new issues with ideally a full reproduction steps (if your project is not open source, please put up a sample repository project with minimum code needed to hit the issue).
Thanks!
@derkjn – It’s unrelated.
inspectpackrequires a specified root package.json to run theversionsaction, which you can see here: https://github.com/FormidableLabs/inspectpack/blob/46081b3d294429a3ac9e521621dac078bd995a57/lib/actions/versions.js#L305-L310I’d open a new issue with your exact setup and file structure including where your
node_moduleslives.Not sure if it’s related but I’m getting stuck at the following error: