SharePoint framework supports modern tool chain
like Node js, NPM, Typescript, Yeomen, Gulp, Javascript coding via React, Angular, Knockout, SharePoint workbench.
The NPM package consist of one or more reusable java script code files called modules. (Node-modules).
SPFX consists of several npm packages.
where are NPM is useful to work with the several npm packages.
like Node js, NPM, Typescript, Yeomen, Gulp, Javascript coding via React, Angular, Knockout, SharePoint workbench.
Node JS -
Node js is an asynchronous event driven java script runtime.The NPM package consist of one or more reusable java script code files called modules. (Node-modules).
SPFX consists of several npm packages.
where are NPM is useful to work with the several npm packages.
YoMEN:
Yomen is a client-side-development stack, consists of several functions in one place and runs through command line interface.
In SPFX, SharePoint generator provide a default template to our spfx solution. In order to create this generator, we need YOMEN.
To sum up, YOMEN is common build tool, boiler plate code(Standard default code),
It provides SharePOint work bench to host webparts for testing.
GULP:
Gulp is basically a task runner.
It converts our SASS files to CSS files and TypeScipt files to Javascript files.
TypeScript
Typescript is a superset of Javascript.
It has features to use concepts like classess, interfaces and modules.
SharePOint WorkBench
SharPoint workbench is used for after build our application, we can test or preview our application with help of workbench.
There are two types of workbenches, one is available locally with SharePOint developer tool chain.
Other with SharePoint developer tenancy.
Package.JSON
Package.json is the created by the following command npm init or npm init --yes
npm init --yes made yes as default to all the questions with respective to the command.
The package.json file is the central to all the node based project.
It can also be consider as a set up of the project.
It allows to install all the dependencies on the local drive and the dependencies getting to the package.json file under dependencies key]
Comments
Post a Comment