[bug] `TypeError: Cannot read properties of undefined (reading 'filter')` when passing stats object

[mjames-c]

Unfortunately, webpack-bundle-analyzer doesn't print an error stack trace so I don't know which property it is expecting that isn't present in the stats file. The top level keys in the stats JSON object are listed below:

cat <omitted>/webpack-stats.json | jq 'keys[]'
"chunks"
"entrypoints"
"errors"
"errorsCount"
"hash"
"namedChunkGroups"
"outputPath"
"publicPath"
"version"
"warnings"
"warningsCount"

cat <omitted>/webpack-stats.json | jq '.chunks[] | select(. != null) | keys[] | limit(1; .)' | sort
"auxiliaryFiles"
"children"
"childrenByOrder"
"entry"
"files"
"hash"
"id"
"idHints"
"initial"
"modules"
"names"
"origins"
"parents"
"recorded"
"rendered"
"runtime"
"siblings"
"size"
"sizes"

[alexander-akait]

@mjames-c Hello, can you create reproducible test repo?

[jonathan-boudreau-work]

With --log-level debug, I was able to find the root cause of this. The assets property can be undefined: https://github.com/webpack/webpack-bundle-analyzer/blob/main/src/analyzer.js#L55

[alexander-akait]

@jonathan-boudreau-work Can you provide a cases when they are undefined? Looks weird

[jonathan-boudreau-work]

We're using dynamic await import() instead of the usual require. I don't think you have test cases for this.

[alexander-akait]

@jonathan-boudreau-work Can you provide more context, where do you use it?

[jonathan-boudreau-work]

We're using ng cli, looks like internally its using vite instead of webpack. So I'd say you can probably close this issue.