Can we reduce both the package size and the package creation time?

[bhoomesh-spe]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

None

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• SPFx version - 1.21.1
• Node.js version - 22.14.0

Describe the bug / error

We have developed an SPFx project that includes 15 web parts.

Please find the attached config.json and package.json files for additional details.

config.json
package.json

The project functions as expected; however, generating the package currently takes a significant amount of time—approximately 8–10 minutes.

The resulting package size is 21 MB.

Steps to reproduce

The following commands were executed during the package generation process:

1. gulp clean
2. gulp bundle --ship
3. gulp package-solution --ship

Expected behavior

We would like to know if there is any way to optimize the package size and reduce the package creation time.

[VesaJuvonen]

@bhoomesh-spe - I'd do the same test with SPFx 1.22 - with one of the example packages and see the outcome. One of the objectives on the SPFx 1.22 was to provide optimized packaging with modern toolchain.

Obviously 21MB is way to much as a package, but that could also contain images which are not optimized, so I doubt that the actual web part code is 21MB - so would have a look also on what's actually getting packaged on the sppkg file.

[kbeverforden]

@VesaJuvonen I'm not the person who created this issue but wanted to ask you if the package sizes were expected to increase in 1.22? Ours went from 16.5 MB in 1.21.1 to 39.3 MB in 1.22 with the exact same number of web parts in each. I extracted the .sppkg files for both and compared the .js file for one web part and it went from 3.8 MB in the old version to 10.8 MB in the new one.

I did a side-by-side comparison of the first 75 lines of each and they look a lot different. The left is v1.21.1 and the right is 1.22. I wasn't sure if this is expected or not.

[VesaJuvonen]

Thx for sharing this @kbeverforden - this is definitely something which we will have a closer look in start of 2026. Clearly optimizations are needed and should be done in those sizes. Thank you for sharing the comparison between 1.21 and 1.22 - super helpful.

Seems that the bundle is not optimized - and that could be caused by multiple reasons. We'll check the implementation and guidance on this for sure 👍

[kbeverforden]

@VesaJuvonen Thanks for looking into it! Here's an overview of some of our biggest web parts and how much they increased in size (bottom). Some more than tripled in size. We use full-page web parts that have a lot of third party libraries (maps, charts, etc).