How to analyze your JavaScript bundles

preview_player
Показать описание
Learn how to analyze your bundled JavaScript code and to spot common issues that can easily bloat up your application size.

Related Playlist:

Speaker:
Houssein Djirdeh

Рекомендации по теме
Комментарии
Автор

To recap:
1. [Chrome dev tools] Network tab (js filter): find how big JavaScript bundles are downloaded
2. [Chrome dev tools] Coverage tab (ctrl + shift + P(Windows)/cmd+shift+P(Mac) and type "coverage"): find how much unused JavaScript code when loading the page
3. [Lib] Webpack-bundle-analyzer: visualize which module makes up the bundle, show size of each module and relations to each other
4. [Lib]Source -map-explorer: visualize treemap of the bundle and identify the problem (lazy load, duplicated, too large code etc)
5. Lighthouse: help analyze how much unused code, potential savings and polyfills that new browsers don't need etc, by using source map

linglingqiu
Автор

Thank you so much. Learned more than I ever expected to learn, and the content relevance to what I was after was spot on! Thank you for speaking clearly, and with great volume. Perhaps the best tutorial I've watched on youtube; ever!

Greatfulone
Автор

Great explanation. Learned a lot. Thanks!!

navin-moorthy
Автор

i love these lil videos, thanks so much hehe

fireystella
Автор

In case anyone wondering how to get NPM Analyze web page.
@4:06 he meant running "ANALYZE=true npm run build" which builds and opens this in your browser.

ajinkyax
Автор

02:29 coverage tab 03:33 webpack-bundle-analyzer, bundle-specific visualization tools 04:40 source maps explorer 06:18 lighthouse, source maps

domaincontroller
Автор

whats the diff between vis of bundles and source map?

hkjpotato
Автор

Or just stop relying on all these heavy front end frameworks to begin with.

bren.r