5/2/2023 0 Comments Update npm versionYou shouldn't edit the package.json file manually. When updating packages to newer versions, you should always use your package manager (npm or Yarn). When working with SharePoint Framework solutions compatible with SharePoint hosted on-premises, you should always verify which patch level the target SharePoint farm has and which version of the SharePoint Framework it supports. If you update your solution to use these latest packages, it no longer works with SharePoint Server 2016. These versions, however, work only with SharePoint Online. When you run the npm outdated command in a project that targets both SharePoint Online and SharePoint Server 2016, it shows you the latest versions of the SharePoint Framework packages. When scaffolding new projects, the SharePoint Framework Yeoman generator prompts you to choose if your solution should be using the latest version of the SharePoint Framework and be working only with SharePoint Online, or if it should use an older version of the SharePoint Framework and work with both SharePoint Server 2016 and SharePoint Online. SharePoint Server 2016 uses an older version of the SharePoint Framework than the version available in SharePoint Online. SharePoint Server 2016 with Feature Pack 2 supports SharePoint Framework solutions. Make sure you read the Release Notes & Roadmap for the specific release to infer which packages require updates. To identify the SharePoint Framework packages, look for the package names that start with the following npm scope and prefix: with the SharePoint Framework packages, you may also need to update react and office-ui-fabric-react packages. Version requested by your project (available in package.json).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |