honeymoose
/
sp-dev-fx-webparts
mirror of https://github.com/pnp/sp-dev-fx-webparts.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Moved links around

Hugo Bernier 2022-03-27 00:46:12 -04:00
parent f0ffb8efcd
commit 8b95800415
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Troubleshooting-issues-with-samples.md

@ -58,7 +58,7 @@ Make sure that you are running `npm install` in the root folder where the web pa
If you're already currently in the root of the sample solution, take a look to see if the sample contains sub-components; are there any folders named `webparts` (or something similar)? If so, try looking for the `README.md` for instructions on how to build the sample. If you're already currently in the root of the sample solution, take a look to see if the sample contains sub-components; are there any folders named `webparts` (or something similar)? If so, try looking for the `README.md` for instructions on how to build the sample.
## Sample won't build ## Diagnose `gulp build` issues
### Most likely cause: Node.js incompatibility ### Most likely cause: Node.js incompatibility
@ -180,10 +180,6 @@ If you are unable to update your environment to run the solution, consider the f
- **Upgrade the sample:** You may be tempted to upgrade the sample to the latest version of SPFx, but doing so may take some time and you may find out that the sample no longer works, or does not meet your needs. Furthermore, you may introduce new bugs that were previously not found in the original version. You should only invest the time to upgrade a sample if you can confirm that the sample works in within a compatible environment, and if you need to add new capabilities that are not supported in previous versions of SPFx, or to fix a vulnerability which can only be fixed with newer versions of SPFx, Node.js, or solution dependencies. - **Upgrade the sample:** You may be tempted to upgrade the sample to the latest version of SPFx, but doing so may take some time and you may find out that the sample no longer works, or does not meet your needs. Furthermore, you may introduce new bugs that were previously not found in the original version. You should only invest the time to upgrade a sample if you can confirm that the sample works in within a compatible environment, and if you need to add new capabilities that are not supported in previous versions of SPFx, or to fix a vulnerability which can only be fixed with newer versions of SPFx, Node.js, or solution dependencies.
## Diagnose `gulp build` issues
To be added later
## Diagnose `gulp serve` issues ## Diagnose `gulp serve` issues
To be added later To be added later