![]() ![]() ![]() The difference in size between the debug and release version of the generated bundle differs depending on the libraries used in your project. The debug version of the bundle is 1255 KB while its release equivalent is only 177 KB. To illustrate the difference, compare the size of the debug and release version of a SharePoint Framework project with a web part using Angular. The main difference between the output of a debug and release build is that the release version of the generated bundle is minified and smaller in size than its debug equivalent. But when your code is finished and is working as expected, you should build it in release mode to optimize it for running in the production environment.įor more information about building your project in release mode, see SharePoint Framework toolchain. By default, SharePoint Framework projects are built in debug mode, which makes it easier for you to debug code. When building a SharePoint Framework project, you can choose whether you want to build it in a debug or release mode. This article illustrates the main differences between debug and release builds and shows how you can optimize your bundle for use in production environments. ![]() Used to control how much details the plugin outputs.When deploying SharePoint Framework solutions to production, you should always use a release build of your project that is optimized for performance. If multiple patterns are provided asset should match at least one of them to be excluded.ĭefault: info. If pattern is a function it should have the following signature (assetName: string) => boolean and should return true to exclude matching asset. If pattern is a string it will be converted to RegExp via new RegExp(str). Patterns that will be used to match against asset names to exclude them from the report. You can choose not to open a window by default: mix.bundleAnalyzer(ĭefault: null. Therefor you must run npm run watch or npm run watch-poll. You might only want to open the analyzer when watching: const mix = require('laravel-mix') Your should look like this: const mix = require('laravel-mix') This extension adds webpack bundle analyzer support to laravel mix Instalation npm install laravel-mix-bundle-analyzer -save-dev Simple analytics for bloggers & businesses. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |