Overview of SPFx
SharePoint Framework is also abbreviated as SPFx. SharePoint Framework offers modern technologies, Node-based development, TypeScript etc. that are applied to SharePoint and Office 365 development.

Earlier, we used to create web-parts (rectangular boxes with defined functionality) and even business users knew what web-parts are. In SharePoint Framework, these web-parts are termed as Client web-parts. From a technology perspective, they are quite different, but from a user perspective, they are the same rectangular widgets that the users can add on their pages. In addition, we know about Add-In model and the Iframe-based integration, which we used in our daily SharePoint development.
History of SharePoint Development
- Farm Solutions
The development in SharePoint started with Farm Solutions, WSPs, full trust code. This approach was very powerful and developers could literally do whatever they wanted to do on the SharePoint Farm. However, it made upgrades very difficult and it made maintaining and keeping the environment secure very difficult. - Sandbox Solutions
A box in which code cannot run outside the boundary of the box. - Add-Ins (App Model)
This has been introduced in SharePoint 2013 and Office 365. It is based on Iframe-based integration. This approach also has many disadvantages. - Script Injection
Using Content Editor and Script Editor web-parts. With this approach, we can almost everything on a SharePoint page; however, this is not the best-recommended approach from Microsoft. - No-script capability
A tenant wide setting which removes all content editor web-part and scripts from the page. - SharePoint Framework
It is a custom and supported way from Microsoft, to allow to embed code inside SharePoint sites.

Skills and Tools required for SPFx
- Npm and Node-based Development
- TypeScript
- Visual Studio Code Editor

NPM and Node-Based Development
The example shown in this article is tested on a Windows 10 Machine (although you can test on a MAC or LINUX machine also). I have installed a terminal called “cmder” - http://cmder.net/ (You can go with built-in terminal also).

Now we will see how to install Node.js
Go to the site nodejs.org, and download and install the Current (Latest features) version of Node.js (.msi file will be downloaded).


Once nodejs is installed in your system, you will see the below folders created in your local drive path,

NOTE









Manjula SiripuramPosted Apr 22, 2019, 10:28 PM
Part 3 link please?
Bhawana KesharwaniPosted Mar 11, 2019, 2:14 PM
Next article link please?
Mahesh BabuPosted Sep 28, 2017, 5:38 AM
Hi Vipil .. thanks for your article. Can you please confirm , which version is recommended for installation? You mentioned in article LTS version not recommended. I think so, LTS version is stable version.
Manoj MittalPosted Sep 21, 2017, 6:37 PM
Nice article. Why scripts injection is not recommended ? Is it going to impact any performance or updates ?