169 lines
8.7 KiB
Markdown
169 lines
8.7 KiB
Markdown
# Version Display
|
|
|
|
## Summary
|
|
|
|
Display your SharePoint solution version within your web parts.
|
|
|
|
|
|
|
|
|
|
## Compatibility
|
|
|
|
| :warning: 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. |
|
|
|
|
|
|
|
|
|
|
|
|
-Incompatible-red.svg "SharePoint Server 2016 Feature Pack 2 requires SPFx 1.1")
|
|
|
|
|
|
|
|
|
|
|
|
For more information about SPFx compatibility, please refer to https://aka.ms/spfx-matrix
|
|
|
|
## Applies to
|
|
|
|
* [SharePoint Framework](https://learn.microsoft.com/sharepoint/dev/spfx/sharepoint-framework-overview)
|
|
* [Microsoft 365 tenant](https://learn.microsoft.com/sharepoint/dev/spfx/set-up-your-development-environment)
|
|
|
|
## Prerequisites
|
|
|
|
There are no pre-requisites.
|
|
|
|
## Contributors
|
|
|
|
* [Hugo Bernier](https://github.com/hugoabernier)
|
|
|
|
## Version history
|
|
|
|
Version|Date|Comments
|
|
-------|----|--------
|
|
1.0|March 31, 2020|Initial release
|
|
2.0|February 7, 2022|Upgraded to SPFx 1.13.1
|
|
|
|
## Minimal Path to Awesome
|
|
|
|
* Clone this repository
|
|
* Set the `version` node in the `package.json` file, or by using `npm version major`, `npm version minor` or `npm version patch`
|
|
* in the command line run:
|
|
* `npm install`
|
|
* `gulp serve`
|
|
|
|
> This sample can also be opened with [VS Code Remote Development](https://code.visualstudio.com/docs/remote/remote-overview). Visit https://aka.ms/spfx-devcontainer for more information.
|
|
|
|
## Features
|
|
|
|
The sample uses a custom `gulp` task to synchronize the `version` node from the NodeJS `package.json` to the SharePoint solution's `package-solution.json`.
|
|
|
|
The solution demonstrates how to import the `package-solution.json` into a web part using a static `import` and a `require` statement.
|
|
|
|
### Using npm version to set the version
|
|
|
|
To change the `package.json` version (which will also change your SharePoint solution version), use [`npm version`](https://docs.npmjs.com/cli/version), using one of the following parameters:
|
|
|
|
```cmd
|
|
npm version major
|
|
npm version minor
|
|
npm version patch
|
|
```
|
|
|
|
The following table shows when you should call which `npm version` command, depending on the types of changes you're making to your solution:
|
|
|
|
|Type of change|Stage|Versioning rule|Example version| NPM command
|
|
|---|---|---|---|---|
|
|
|First release|New solution|Start with 1.0.0|1.0.0| `npm version major`
|
|
|Backward compatible bug fixes|Patch release|Increment the third digit|1.0.1| `npm version patch`
|
|
|Backward compatible new features|Minor release|Increment the middle digit and reset last digit to zero|1.1.0| `npm version minor`
|
|
|Changes that break backward compatibility|Major release|Increment the first digit and reset middle and last digits to zero|2.0.0| `npm version major`
|
|
|
|
### To use the custom gulp task in your solutions
|
|
|
|
> NOTE: if you use the [PnP SPFx Yeoman generator](https://pnp.github.io/generator-spfx/), there is already a built-in `gulp` command that will synchronize your version number when you use `npm version`. You only need to follow the steps below if you use the regular SPFx Yeoman generator.
|
|
|
|
If you'd like to use the custom `gulp` task in your solutions, copy the code from this solution's `gulpfile.js` between:
|
|
|
|
```typescript
|
|
// BEGIN: Add custom version sync task
|
|
```
|
|
|
|
and
|
|
|
|
```typescript
|
|
// END: Add custom version sync task
|
|
```
|
|
|
|
To your own `gulpfile.js`.
|
|
|
|
### To use the version using the web part's manifest
|
|
|
|
The `BaseClientSideWebPart` class `context` property provides a `manifest` which contains a `version` property. To use it in your web part, simply use:
|
|
|
|
```typescript
|
|
this.context.manifest.version
|
|
```
|
|
|
|
This approach provides a version number that follows the `1.0.0` format, instead of the usual `1.0.0.0` format. However, since the `gulp` tasks describe above append an additional `.0` to the end of the `package.json` version number, you can choose to append `.0` yourself when displaying the manifest version. For example:
|
|
|
|
```typescript
|
|
this.context.manifest.version + '.0'
|
|
```
|
|
|
|
### To use the version using a static import
|
|
|
|
1. Copy the content of this solution's `src\typings.d.ts` to your own `src` folder in your own project.
|
|
2. In the code where you want to insert the solution version, add the following `import` statement:
|
|
```typescript
|
|
import * as packageSolution from '../../../config/package-solution.json';
|
|
```
|
|
|
|
Keep in mind that you may have to adjust the path to your `package-solution.json` depending on where you're adding the code within your solution.
|
|
|
|
### To use the version using a require
|
|
|
|
In the code where you want to insert the solution version, add the following `require` statement:
|
|
```typescript
|
|
const packageSolution: any = require("../../../config/package-solution.json");
|
|
```
|
|
|
|
Keep in mind that you may have to adjust the path to your `package-solution.json` depending on where you're adding the code within your solution.
|
|
|
|
## For More Information
|
|
|
|
If you'd like to read more about the concepts illustrated in this sample, please refer to the following links:
|
|
|
|
* [Semantic Versioning](https://semver.org/)
|
|
* [npm version](https://docs.npmjs.com/cli/version)
|
|
* [PropertyPaneWebPartInformation](https://sharepoint.github.io/sp-dev-fx-property-controls/controls/PropertyPaneWebPartInformation/)
|
|
* [Displaying the solution version in your web part](https://tahoeninja.blog/2020/03/30/display-the-solution-version-in-your-web-part/)
|
|
* [How to version new SharePoint Framework projects](https://n8d.at/how-to-version-new-sharepoint-framework-projects/)
|
|
|
|
|
|
## 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.
|
|
|
|
If you're having issues building the solution, please run [spfx doctor](https://pnp.github.io/cli-microsoft365/cmd/spfx/spfx-doctor/) from within the solution folder to diagnose incompatibility issues with your environment.
|
|
|
|
You can try looking at [issues related to this sample](https://github.com/pnp/sp-dev-fx-webparts/issues?q=label%3A%22sample%3A%20react-versiondisplay") to see if anybody else is having the same issues.
|
|
|
|
You can also try looking at [discussions related to this sample](https://github.com/pnp/sp-dev-fx-webparts/discussions?discussions_q=react-versiondisplay) and see what the community is saying.
|
|
|
|
If you encounter any issues while using this sample, [create a new issue](https://github.com/pnp/sp-dev-fx-webparts/issues/new?assignees=&labels=Needs%3A+Triage+%3Amag%3A%2Ctype%3Abug-suspected%2Csample%3A%20react-versiondisplay&template=bug-report.yml&sample=react-versiondisplay&authors=@hugoabernier&title=react-versiondisplay%20-%20).
|
|
|
|
For questions regarding this sample, [create a new question](https://github.com/pnp/sp-dev-fx-webparts/issues/new?assignees=&labels=Needs%3A+Triage+%3Amag%3A%2Ctype%3Aquestion%2Csample%3A%20react-versiondisplay&template=question.yml&sample=react-versiondisplay&authors=@hugoabernier&title=react-versiondisplay%20-%20).
|
|
|
|
Finally, if you have an idea for improvement, [make a suggestion](https://github.com/pnp/sp-dev-fx-webparts/issues/new?assignees=&labels=Needs%3A+Triage+%3Amag%3A%2Ctype%3Aenhancement%2Csample%3A%20react-versiondisplay&template=question.yml&sample=react-versiondisplay&authors=@hugoabernier&title=react-versiondisplay%20-%20).
|
|
|
|
|
|
## 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.**
|
|
|
|
|
|
<img src="https://m365-visitor-stats.azurewebsites.net/sp-dev-fx-webparts/samples/react-versiondisplay" />
|