Is it normal for sppkg file to jump from 521k to 732k just by adding people picker

Category

• Enhancement
• Bug
• Question

Version

Latest

Expected / Desired Behavior / Question

I installed the latest version to get the People Picker and my finished sppkg file went from 521k to 732k. Is this normal? I presume it is loading the entire library and not just the people picker. Is there a way to trim down what is imported?

Question 2: If I deploy my webpart so that you need to install it on every site through Add an App, does it basically have to cache a site-specific copy of the webpart.js? Or does it just load a cached version pointing back to the tenant app catalog?

Question 3: If I do add this install, does it impact the gulp serve --nobrowser webpart update process? ie make it a lot longer to see the update in the browser after I save my file in VS code?

I guess 200k is not that large when compared to images but since it is required to load before the page can be rendered, it is a little more important than images which load after.

This is all I’m using at the moment.

import { PropertyFieldPeoplePicker, PrincipalType } from '@pnp/spfx-property-controls/lib/PropertyFieldPeoplePicker';

Thanks!

[mikezimm]

@joelfmrodrigues , Yep I run gulp clean every time but thanks for the reminder.

@AJIXuMuK , Thanks for the answers to the questions!

[AJIXuMuK]

I’ll close the issue. Let us know @mikezimm if you need any additional help.