Tag: Gulp

 

Something that is giving me some trouble for a long time is that the SharePoint Framework build process treads warnings as errors in production builds (when the –ship flag is present). Let’s start by giving some background information. During bundling/packaging of your SharePoint Framework solution, you could see two types of messages:

 

When building custom gulp tasks in your SharePoint Framework solutions, it might be handy to log as the default build system does. More information about building custom gulp tasks can be found here: Integrate gulp tasks in SharePoint Framework toolchain When you would use the default console.log, console.warn,** **or console.

 

Automating your builds and releases for SharePoint Framework is easy to achieve on Azure DevOps. In the past, I have written how you can achieve it by using custom Gulp tasks or using the Office 365 CLI. One thing both solutions have in common is that they are taking 5-10 minutes to complete.

 

This article is an addition to my previous one about how to automate the publication process of your JavaScript file to Office 365 public CDN. Related article: Automate publishing of your SharePoint Framework scripts to Office 365 public CDN Not long after I had published my previous article, I got the following question on Twitter:

 

Last year Microsoft announce the Office 365 public CDN capability. This is CDN option from Office 365 is a great way for you to host your assets like images or JavaScript files. Most important, this is probably the easiest option for publishing your SharePoint Framework client-side web part assets. This is because it does not require you to setup anything on Azure.

 

webpack After the introduction of Node.js, npm, Gulp and Yeoman. It is time to spend some time on another tool called webpack. Webpack is a module bundler and is one of the tools which is used in the building process of a SharePoint Framework client-side web part.