This makes it possible to collect just modules that are used in your program. Webpack works by traversing your source tree starting from some "entry" modules and navigating through module imports.
![burst requires the android ndk to be correctly installed burst requires the android ndk to be correctly installed](https://i.stack.imgur.com/lEjln.png)
With NativeScript 6 and above, Webpack is the primary developer workflow and can't be disabled. With the advent of ECMAScript 2015 modules, we have new tools that allow stripping unused parts of big modules and further reduce our application size.
![burst requires the android ndk to be correctly installed burst requires the android ndk to be correctly installed](https://i.stack.imgur.com/p3K6w.png)
Not using that obscure feature in module X? Don't make your users pay for it then. Bundlers traverse the module import graph and do not bundle unused modules. Mobile file storage is not known for being very performant.
BURST REQUIRES THE ANDROID NDK TO BE CORRECTLY INSTALLED CODE
![burst requires the android ndk to be correctly installed burst requires the android ndk to be correctly installed](https://docs.godotengine.org/es/stable/_images/andtemplates.png)
Why bundle scripts in a mobile app though? Aren't all files stored on the local device, so requesting them should be faster than an HTTP request? Yes, that is the case, but bundling still has an essential place in mobile app optimizations: Most importantly, they allow for page load time optimizations that reduce or parallelize the number of requests a browser makes to the server. Tools like Webpack have been providing support for an enjoyable development experience that lets you assemble client-side code from various module sources and formats and then package it together. JavaScript code and general asset bundling have been a member of the web developer toolbox for a long time.