Book Image

SharePoint Development with the SharePoint Framework

By : Jussi Roine, Olli Jääskeläinen
Book Image

SharePoint Development with the SharePoint Framework

By: Jussi Roine, Olli Jääskeläinen

Overview of this book

SharePoint is one of Microsoft's best known web platforms. A loyal audience of developers, IT Pros and power users use it to build line of business solutions. The SharePoint Framework (SPFx) is a great new option for developing SharePoint solutions. Many developers are creating full-trust based solutions or add-in solutions, while also figuring out where and how SPFx fits in the big picture. This book shows you how design, build, deploy and manage SPFx based solutions for SharePoint Online and SharePoint 2016. The book starts by getting you familiar with the basic capabilities of SPFx. After that, we will walk through the tool-chain on how to best create production-ready solutions that can be easily deployed manually or fully automated throughout your target Office 365 tenants. We describe how to configure and use Visual Studio Code, the de facto development environment for SPFx-based solutions. Next, we provide guidance and a solid approach to packaging and deploying your code. We also present a straightforward approach to troubleshooting and debugging your code an environment where business applications run on the client side instead of the server side.
Table of Contents (14 chapters)

Optimizing the SharePoint Framework packages

When you start building solutions with SPFx, there's a nice way to view what kind of packages you are producing. As part of the toolchain, Microsoft has included Webpack Visualizer, which produces a nice overview of your overall bundle. This overview is accessible under /temp/stats, in a .html file:

This sample SPFx web part project is about 20 KB without any optimizations.

To deploy code in production, as discussed in Chapter 6, Packaging and Deploying Solutions, use the ship parameter with gulp bundle to minify the dependent packages:

We can see from the preceding output that instead of a DEBUG build, this will be a SHIP build. The WEBPACK VISUALIZER now shows an, even more, slimmed-down release:

From roughly 20 KB down to 6.8 KB, this is about 65 % smaller with just one command. This is even more evident in larger projects.