d134aed45f
Bumps [browserify-sign](https://github.com/crypto-browserify/browserify-sign) from 4.2.1 to 4.2.2. - [Changelog](https://github.com/browserify/browserify-sign/blob/main/CHANGELOG.md) - [Commits](https://github.com/crypto-browserify/browserify-sign/compare/v4.2.1...v4.2.2) --- updated-dependencies: - dependency-name: browserify-sign dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> |
||
---|---|---|
.. | ||
.devcontainer | ||
assets | ||
config | ||
src/webparts | ||
README.md | ||
gulpfile.js | ||
package-lock.json | ||
package.json | ||
tsconfig.json |
README.md
page_type | products | languages | extensions | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
sample |
|
|
|
Angular Elements in SharePoint Framework
Summary
Set of sample web parts illustrating how to use Angular Elements in the SharePoint Framework.
Compatibility
⚠️ Important |
---|
Every SPFx version is only compatible with specific version(s) of Node.js. In order to be able to build this sample, please ensure that the version of Node on your workstation matches one of the versions listed in this section. This sample will not work on a different version of Node. |
Refer to https://aka.ms/spfx-matrix for more information on SPFx compatibility. |
Applies to
Contributors
- Waldek Mastykarz ,
- Sébastien Levert (MVP, Valo, @sebastienlevert)
Version history
Version | Date | Comments |
---|---|---|
1.0 | June 1, 2018 | Initial release |
Minimal Path to Awesome
- clone this repo
- in the command line run:
npm i
gulp serve
This sample can also be opened with VS Code Remote Development. Visit https://aka.ms/spfx-devcontainer for further instructions.
Features
This sample contains a set of web parts that illustrate using Angular Elements in the SharePoint Framework.
This web part illustrates the following concepts on top of the SharePoint Framework:
- adding Angular Elements to a no-framework SharePoint Framework project
- bootstrapping Angular Elements inside a SharePoint Framework web part
- extending the building configuration to build Angular Elements
- checking if the particular web component has already been registered to avoid conflicts
- passing web part configuration to Angular Elements and reacting to configuration changes
- calling the SharePoint REST API from an Angular Element using the native Angular HttpClient
- calling the Microsoft Graph from an Angular Element using the SharePoint Framework MSGraphClient
- calling the SharePoint REST API from an Angular Element using PnPjs
- calling the Microsoft Graph from an Angular Element using PnPjs
Help
We do not support samples, but we this community is always willing to help, and we want to improve these samples. We use GitHub to track issues, which makes it easy for community members to volunteer their time and help resolve issues.
You can try looking at issues related to this sample to see if anybody else is having the same issues.
You can also try looking at discussions related to this sample and see what the community is saying.
If you encounter any issues while using this sample, create a new issue.
For questions regarding this sample, create a new question.
Finally, if you have an idea for improvement, make a suggestion.
Disclaimer
THIS CODE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.