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.