You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2021. It is now read-only.
It appears that bundle-analyzer will correctly gather stats from a webpack config file that exports multiple configurations. However each configuration goes to a specific record in bundle-analyzer. As an example if I have a webpack config file with 4 configurations, there will be 4 builds recorded in bundle-analyzer for that single pull/commit hash.
My question is, will this result in multiple checks (one for each build) showing up in the github pull checks ui, or does it just show the latest build to be received?
The text was updated successfully, but these errors were encountered:
It appears that only a single check makes it through to the UI. It'd be nice to be able to provide a key in .bundle-analyzerrc or environment variables to make the check names unique; that way the monorepo use case would be a bit better supported.
(I'm using bundle-analyzer on a repo which has ~12 separate invocations of webpack per commit, mostly because of things like serverless-webpack but there is also more than one frontend codebase in the repo, so even ignoring that I'd need some way to split the checks)
It appears that bundle-analyzer will correctly gather stats from a webpack config file that exports multiple configurations. However each configuration goes to a specific record in bundle-analyzer. As an example if I have a webpack config file with 4 configurations, there will be 4 builds recorded in bundle-analyzer for that single pull/commit hash.
My question is, will this result in multiple checks (one for each build) showing up in the github pull checks ui, or does it just show the latest build to be received?
The text was updated successfully, but these errors were encountered: