How is SPFX webparts deployed to SharePoint library?
The build output of SPFx client side webpart consists of a solution package (.sppkg file) and various scripts, CSS, and other assets. The sppkg file is deployed to SharePoint which includes manifest with URL pointing to the location where script files are deployed.
Where to find the package version number in SPFX?
Looking for a way to grab the package version number (that is, the value of solution.version that is stored in package-solution.json and which is displayed in the app catalog) and render it in a hidden field in the web part, so that we can have our test harness inspect it across site pages. I see that the ISolution interface has this property.
How to deploy sharepoint client side web part?
Select SharePoint Online only (latest), and select Enter. Select Use the current folder for where to place the files. Select y to use the tenant-scoped deployment option, which makes the web part available across sites immediately when it’s deployed. Select N on the question if solution contains unique permissions.
Can a SharePoint framework be deployed to a CDN?
SharePoint Framework does not impose any restrictions that scripts should be deployed to any CDN. You can upload the scripts anywhere from where it can be accessed. That means you can even upload the scripts to a SharePoint library inside your tenant to which everyone has an access.
Where is the sppkg file deployed to SharePoint?
The sppkg file is deployed to SharePoint which includes manifest with URL pointing to the location where script files are deployed. The script files should exist at the location specified in the manifest file, otherwise, the web part will not work in SharePoint. These files usually get deployed to a CDN location.
When to provision SharePoint assets with your solution package?
If the user doesn’t have sufficient permissions to create or modify SharePoint items, the JavaScript code does not provision those items. In such cases, when you want to provision SharePoint items in an elevated context, you must package and deploy the items along with your solution package.
https://www.youtube.com/watch?v=SfzdOX8MzdY