SharePoint PnP Webcast – Reuse your existing JavaScript libraries with SharePoint Framework

In this PnP Webcast, we concentrated on covering the steps on how you can reuse your existing investments on JavaScript when developing with SharePoint Framework solutions. Lot of customers and partners have developed their existing plan JavaScript libraries, which have been used with custom web parts or using script editor web part. You do not need to rebuild these to be able to take advantage of them with SharePoint Framework solutions, but there are few steps for making them usable, which are being presented in this webcast. In general, we do recommend usage of TypeScript on development time, since it provide multiple benefits, but that's not a hard requirement and you can use your existing plan JavaScript customizations as such also with SharePoint Framework. 

Notice. When this webcast was released, SharePoint Framework was available as a Developer Preview release.  

Presentation covers following topics:

  • Options for using existing JavaScript libraries in SharePoint Framework solutions
    • Reference exteranl libraries from URL
    • Include JavaScript directly to your solution
    • Reference NPM packages
  • Considerations when you use your own scripts
    • You will need to adjust your script and markup to support modular access
    • You can use plain JavaScript directly with TypeScript
    • You can reuse easily your existing investments on plain JavaScript

Web cast demo (6:40) shows following details

  • Use case - using custom library with classic script editor web part
  • How your custom JavaScript files are bundled to the JavaScript files with SharePoint Framework
  • Steps to make your custom JavaScript working with SharePoint Framework solutions
  • Considerations around adding event receivers on the html components used in SharePoint Framework solutions

Webcast presenters: Waldek MastykarzVesa Juvonen

Presentation used in this web cast is available from http://docs.com/OfficeDevPnP.

Video at YouTube.

Additional resources

See following resources around the SharePoint Framework. 

What is SharePoint / Office DevPatterns & Practices (PnP) web cast series?

SharePoint / Office Dev Patterns and PracticesSharePoint / Office Dev Patterns & Practices (PnP) webcast series covers different patterns, practices and topics around development with Office 365 and SharePoint. Majority of the topics are valid for the Office 365 and SharePoint on-premises. Our objective is to release new around 30 minute long web cast each Monday with few slides and a live demo on the covered topic. All web casts are published at the PnP YouTube channel with additional references on the existing materials.

PnP is community driven open source project where Microsoft and external community members are sharing their learning's around implementation practices for Office 365 and SharePoint on-premises (add-in model). Active development and contributions happen in our GitHub repositories under dev branch and each month there will be a master merge (monthly release) with more comprehensive testing and communications. Latest activities and future plans are covered in our monthly community calls which are open for anyone from the community. Download invite from http://aka.ms/SPPnP-Call

This is work done by the community for the community without any actual full time people. It’s been great to find both internal and external people who are willing to assist and share their learning's for the benefit of others. This way we can build on the common knowledge of us all. Currently program is facilitated by Microsoft, but already at this point we have multiple community members as part of the Core team and we are looking to extend the Core team with more community members.

If you have any questions, comments or feedback around PnP program or this blog post, please use the Microsoft Tech Community (SharePoint Developer group).

“Sharing is caring”


Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 7th of November 2016

Comments powered by Disqus