cabal-auto-expose VS webpack-bundle-analyzer

cabal-auto-expose

We haven't tracked posts mentioning cabal-auto-expose yet.
Tracking mentions began in Dec 2020.

webpack-bundle-analyzer

• Bundle size analyzer when using esbuild?
  1 project | /r/Angular2 | 1 Jun 2023

  I used to use webpack-bundle-analyzer but we have switched the builder to browser-esbuild now.

• How to handle multiple webpacks in the same app, that both include React?
  1 project | /r/reactjs | 20 Mar 2023

  First start by running a webpack bundle analysis to see what exactly is bundled. You might be surprised about things being included that you didn't expect which can help with where to look.

• Building a PNPM monorepo with Webpack - large builds?
  1 project | /r/Frontend | 4 Mar 2023

  Firstly I recommend taking a look at the structure of the webpack output with something like webpack-bundle-analyzer for any obvious over bundling issues.

• First time i encounter this any idea how to exploit it ? or its already an info disclosure and i should report within bug bounty program ?
  1 project | /r/bugbounty | 27 Feb 2023

  See: https://github.com/webpack-contrib/webpack-bundle-analyzer

• Web Performance Resources for Front End Developers
  2 projects | dev.to | 4 Jan 2023

  Webpack Bundle Analyzer

• Beautiful Visualizations For Your App's Dependencies
  1 project | /r/javascript | 31 Oct 2022
• 🚀 Angular 14 + ESLint, Material + Transloco + Jest, TestCafe + Docker + Prettier 🚀
  2 projects | dev.to | 25 Sep 2022

  npm run analyse - analyse bundle with webpack-bundle-analyzer

• I shaved 80 MB from my TypeScript build by removing googleapis
  5 projects | news.ycombinator.com | 1 Aug 2022

  This was my question as well. The article does answer the question, but off the bat I'd assumed the author was talking about output/dist. The web treemap cli is a great tip. If you are using webpack, webpack-bundle-analyzer is a helpful tool for quickly finding bloated packages. It's definitely helped me cut down my build times: https://github.com/webpack-contrib/webpack-bundle-analyzer

• Zero experience with Angular. I'm in charge of our CI and we're getting extremely slow prod build times (~1 hour 34 mins). Where should I start researching solutions for this?
  3 projects | /r/angular | 1 Feb 2022

  Here are a few tipps where you could save some time: 1)check angular.json (configurations -> "your ci config") - look for buildOptimizer / optimization 2)If you run npm ci during your pipeline it might make sense to create the node modules folder beforehand, it seems to save time (https://github.com/npm/cli/issues/2011) 3)Use ng build --stats-json to analyze your build 4)Use https://github.com/webpack-contrib/webpack-bundle-analyzer (also works together with 3. ) 5)Check your package.json for unused dependencies 6)Check your imports, import only what is needed Hope this helps

• The best Angular 13 Starter Project
  12 projects | dev.to | 22 Jan 2022

  - `npm run start` - Start the app - `npm run lint` - Lint the project - `npm run test` - Run unit tests - `npm run build` - Build the project - `npm run build:prod` - Build the project in production mode - `npm run build:prod:stats` - Build the project in product mode with stats - `npm run analyse` - Analyse bundle with [webpack-bundle-analyzer](https://github.com/webpack-contrib/webpack-bundle-analyzer) - `npm run compodoc` - Generate [compodoc](https://github.com/compodoc/compodoc) documentation - `npm run version` - Generate changelog - `npm run prettier` - Format the whole project - `npm run audit` - Audit this application using Sonatype OSS Index