smooth-code/bundle-analyzer

Keep your webpack bundle optimized over time 📦✨

bundle-analyzer's Issues

Fix doc link

https://twitter.com/skjnldsv/status/1179335530695315457

Fix back to app link in docs

Error: request entity too large

I just added production source maps to our webpack build and started getting an error that the request entity is too large. I noticed that this lib is sending every file that webpack processes to the server. I'm guessing that the source map files are being sent over too which causes this error to occur.

I'm not sure how other people are using this lib but I really only care about the files that have budgets and I don't really need info on the other files.

Maybe there could be some sort of filter or ignore list that we could specify in the plugin options. Something like

new BundleAnalyzerPlugin({
   token: '<repository-token>',
   ignore: ['*.js.map', '*.{jpg,png}']
})

Configure size compare to not use compression

I have configured size-limit to not use compression, also would like to apply same for size compare but not able to find it. Is there way to configure it?

No size limit configured on the project

I implemented BundleAnalyzer exactly following the documentation, but I keep seeing "No size limit configured on the project" in the BundleAnalyzer app. I tried multiple ways of adding the config:

• I created a bundle-analyzer.config.js file in the root of our project
• I tried adding the configFile option to the Webpack plugin
• I even tried adding the config to the Settings > Configuration in the app directly

Am I missing something? The rest of the checks are working correctly.

Does bundle-analyzer support multiple configurations

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?

Bundle analyzer API throwing 500 internal server error

{
  "message": "Request failed with status code 500",
  "name": "Error",
  "stack": "Error: Request failed with status code 500\n    at createError (/Volumes/Case Sensitive Partition/wielki-janusz/web/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/Volumes/Case Sensitive Partition/wielki-janusz/web/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/Volumes/Case Sensitive Partition/wielki-janusz/web/node_modules/axios/lib/adapters/http.js:236:11)\n    at IncomingMessage.emit (events.js:333:22)\n    at endReadableNT (_stream_readable.js:1201:12)\n    at processTicksAndRejections (internal/process/task_queues.js:84:21)",
  "config": {
    "url": "https://api.bundle-analyzer.com/builds",
    "method": "post",
    "data": "{\"token\":\"<TOKEN_HERE>\",\"bundleId\":\"1edc84e9-1fcb-4b32-aded-d054669be965\",\"branch\":\"feature/mini-switch-styles\",\"commit\":\"69ec234d19814dc5b12d24ff5244f234e9a3658b\",\"providerMetadata\":{\"name\":\"git\",\"commit\":\"69ec234d19814dc5b12d24ff5244f234e9a3658b\",\"branch\":\"feature/mini-switch-styles\"},\"config\":null}",
    "headers": {
      "Accept": "application/json, text/plain, */*",
      "Content-Type": "application/json;charset=utf-8",
      "User-Agent": "axios/0.19.2",
      "Content-Length": 330
    },
    "transformRequest": [
      null
    ],
    "transformResponse": [
      null
    ],
    "timeout": 0,
    "xsrfCookieName": "XSRF-TOKEN",
    "xsrfHeaderName": "X-XSRF-TOKEN",
    "maxContentLength": -1
  }
}

The api keeps 500ing on some of my builds for some of branches. Other branches seem to be fine. Can provide additional debug info if needed.

Support fork for GitHub Checks

Creating a PR from a fork of the repo doesn't trigger GitHub Checks for the bundle analyzer.

For example:

• that one coming from a fork has no checks: #20
• that one coming from a branch of the repo has checks: #12

Following https://twitter.com/j0k/status/1185189452307718145

Document now issue

https://twitter.com/_dte/status/1179334838031196160

Does the comparison is against the master branch?

I've seen other tools that they compare but just against the previous commit in the same branch

How to use "bundle-analyzer" with Angular CLI bundle

I have an Angular 7 application and Angular itself takes care of it's bundling. So how can I use Bundle-analyzer with my application?

Details link in `bundle-analyzer` gh status is broken

Great tool, thanks for the OSS love!

Artsy is trailing this on our main site repo. You can see the PR to add it here: artsy/force#4684.

I noticed that the details link is broken here:

It links to https://github.com/artsy/force/pull/%7B%7D which 404s. The other two detail links (size and diff) both link correctly to the dashboard. Is this supposed to go to the dashboard?

The bundle analyzer app appears to be down

Loading up https://app.bundle-analyzer.com/ gives a blank page

Taking a look at the network requests, there's a 503 "Service Unavailable" api call to https://api.bundle-analyzer.com/graphql for the query

query User {
    user {
        id
        login
        latestSynchronization {
            id
            jobStatus
            __typename
        }
        installations {
            id
            latestSynchronization {
                id
                jobStatus
                __typename
            }
            __typename
        }
        __typename
    }
}

Edit: if there is something I could contribute to get this working again, I'd be happy to help, although this seems like a devops issue with heroku

Not correctly detecting QA branch builds

Thanks for this really helpful utility! We have this deployed in our GitHub organization but it seems to be having problems differentiating between a commit to master and a commit to qa. In the screenshot attached, where it says Branch master, it should say Branch qa. If you click on the hyperlinked commit reference this indeed takes you to a Github page which says Branch qa.

As such, we miss some of the nice features you seem to have implemented where it automatically would show the difference in bundle size between qa and master, which would be really helpful to us.

Is there some set up we are missing or is this an issue with the plugin?

Bundle analyzer randomly failing with 503

Not sure if it's related to #28, since status code it 503 and not 500. Those cases it does not fail, it takes significant time (up to 120 seconds, while without bundle analyzer it takes up to 20 seconds).

> npx webpack --config webpack.ci.js "--env.BUNDLE_ANALYZER_TOKEN=****************************************"
 
Error: Bundle Analyzer - Request failed with status code 503
    at /app/node_modules/@bundle-analyzer/webpack-plugin/lib/index.js:32:18
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

Github check does not appear

Hey!

Thanks for your awesome app, looks very promising!
https://github.com/skjnldsv/vueexample/pull/237/checks

Just enabled this, and I can see the results just fine https://app.bundle-analyzer.com/gh/skjnldsv/vueexample
But there is no github checks on my pull requests. Anything I need to do?