Learn about the dev machine and the important versions displayed in this course.
- Let's start our journey of SPFX by learning how to write web parts, but before I can dive into code, let me introduce you to my development machine. You can follow this course on a Mac, Linux, or Windows machine, but I am choosing to use a Windows machine. The steps and the setup are nearly identical. I have talked about this in other courses. I have a browser, a terminal that I prefer to use, called Commander.
You can also use PowerShell or Git Bash, if you wish. I already have Node.js install, let me show you the version of it. And I have also installed an updated NPM. Also, I would like to show you the global packages that I have install on this machine. So npm list -g --depth=0. And you see there I have the SharePoint generator 1.4.1 installed, and Gulp, and Yarn, and Yeoman.
Undoubtedly, these versions will iterate further, but I thought it was important for you to know the versions with which this course has been recorded. I also have a development Office 365 tenancy. This tenancy is something that I have 100% administrative rights to. So let me go ahead and visit that tenancy. Let's visit Office 365. I'm going to go ahead and sign in, and here, let's visit the admin center, and also let's visit the SharePoint area.
In the SharePoint area, I have previously been playing with some modern sites. In the admin center, if I go to Admin centers, look for SharePoint, here I have already provisioned an app catalog. Also, I have provision myself a test classic, a classic site collection. So Sharepoint Framework works both in classic site collections and modern site collections, so for dev purposes, I have both.
Let me go ahead and clean out this page, because we'll be using this surface to drop our web parts in, so let's go head and remove these web parts so we have a clean surface to play with. Similarly, in the SharePoint area, I clicked this Create button, and I went ahead and created a team site. I've already gone through this process, but you should have a team site for your purposes.
My modern team site lives at /site/taskmodern2. Let's go ahead and clean up this page, as well. See these web parts are actually written with SharePoint Framework, so our web parts are going to show up in a similar area. Let's go ahead and delete the out-of-the-box web parts, and choose to publish this page.
This is my dev environment, and at this point, I am ready to start writing some SharePoint Framework web parts, and other SharePoint Framework artifacts.
- Creating SPFx web parts
- Debugging SPFx web parts
- Deploying SPFx solutions with an Office 365 CDM
- Provisioning SharePoint assets
- Deploying application customizers
- Creating field customizers
- Building command sets