Book Image

Learn ECMAScript - Second Edition

By : MEHUL MOHAN, Narayan Prusty
Book Image

Learn ECMAScript - Second Edition

By: MEHUL MOHAN, Narayan Prusty

Overview of this book

Learn ECMAScript explores implementation of the latest ECMAScript features to add to your developer toolbox, helping you to progress to an advanced level. Learn to add 1 to a variable andsafely access shared memory data within multiple threads to avoid race conditions. You’ll start the book by building on your existing knowledge of JavaScript, covering performing arithmetic operations, using arrow functions and dealing with closures. Next, you will grasp the most commonly used ECMAScript skills such as reflection, proxies, and classes. Furthermore, you’ll learn modularizing the JS code base, implementing JS on the web and how the modern HTML5 + JS APIs provide power to developers on the web. Finally, you will learn the deeper parts of the language, which include making JavaScript multithreaded with dedicated and shared web workers, memory management, shared memory, and atomics. It doesn’t end here; this book is 100% compatible with ES.Next. By the end of this book, you'll have fully mastered all the features of ECMAScript!
Table of Contents (18 chapters)
Title Page
PacktPub.com
Contributors
Preface
Index

Tree shaking


Tree shaking is basically a term used by module bundlers such as WebPack and Rollup to convey that the import-export module syntax can be used for dead-code elimination.

Essentially, the new module loader system enables these module bundlers to do something known as tree shaking, where they shake the tree to get rid of the dead leaves.

Your JavaScript is a tree. The modules you import represent the living leaves of your tree. The dead (unused) code is represented by the brown, dead leaves of the tree. To remove dead leaves, the bundler has to shake the tree and let them fall. 

How tree shaking is performed

Tree shaking, used by a module bundler, eliminates unused code in the following manner:

  1. Firstly, the bundler will combine all of the imported module files (like a good bundler). Here, exports that are not imported in any file are not exported at all.
  2. After that, the bundler minifies the bundle and simultaneously removes dead code. Thus, variables/functions that are not exported...