{"id":1315,"date":"2018-05-10T21:46:02","date_gmt":"2018-05-11T04:46:02","guid":{"rendered":"https:\/\/officedevblogs.wpengine.com\/?p=1315"},"modified":"2021-10-18T11:29:52","modified_gmt":"2021-10-18T18:29:52","slug":"updates-from-build-new-improvements-for-sharepoint-framework-coming-soon","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/updates-from-build-new-improvements-for-sharepoint-framework-coming-soon\/","title":{"rendered":"Updates from Build: New improvements for SharePoint Framework coming soon"},"content":{"rendered":"<p>At Microsoft Build, we previewed several upcoming changes and improvements coming to SharePoint Framework. You\u2019ll see these changes start to release over the coming weeks, and we\u2019ll go into more detail at the upcoming SharePoint Conference \u2013 North America.\u00a0<a href=\"https:\/\/channel9.msdn.com\/events\/Build\/2018\/BRK2409\">Watch Vesa Juvonen\u2019s presentation from Build<\/a>\u00a0to see more detail\u00a0around these new components.<\/p>\n<p><strong>SharePoint Framework 1.5 \u2013 New Flexibility for Retrieving\u00a0Packages<\/strong><\/p>\n<p>SharePoint Framework (SPFx) 1.5 will focus on continuing to respond to feedback and incorporate stability fixes. Numerous issues \u2013 based on your feedback \u2013 have been addressed and are included.<\/p>\n<p>We are also adding new choices for using different types of package managers within SPFx, to provide more flexibility in how you retrieve new packages. You can get packages via the\u00a0<strong>yarn<\/strong>\u00a0and\u00a0<strong>pnpm<\/strong>\u00a0package managers via this new flexibility.<\/p>\n<p><strong>New Releases with Experimental Components<\/strong><\/p>\n<p>Starting with SharePoint Framework version 1.5, you\u2019ll be able to opt-in to new experimental packages, which extend the set of stable packages that SPFx releases will include.<\/p>\n<p>These experimental packages deliver new features that are still under consideration and under development. For any new experimental component, we really value your feedback via\u00a0<a href=\"https:\/\/github.com\/SharePoint\/sp-dev-docs\/issues\">SharePoint GitHub issues<\/a>. Keep in mind, however &#8211; any experimental feature may never be released, or may undergo significant changes before it\u2019s ready to use with your customers \u2013 so please don\u2019t release any SharePoint Framework apps that use experimental features.<\/p>\n<p><strong>Global Deployment of SharePoint Framework Extensions<\/strong><\/p>\n<p>Today, SharePoint Framework Extensions require installing an app within individual site collections. This specificity is useful for departmental scenarios, where you want to have a very extensively customized portal and don\u2019t want the customizations for that portal to become available in other sites.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devofficecdn.azureedge.net\/media\/Default\/Blogs\/csitefooter.png\" alt=\"\" width=\"817\" height=\"500\" \/><\/p>\n<p><em>Deploy standard footers across your tenancy, along with other types of extensions, with global deployment of SharePoint\u00a0Framework extensions<\/em><\/p>\n<p>We\u2019ve also seen that a number of SharePoint Framework Extension scenarios work best when broadly applied across your SharePoint tenancy. For example, customers may want a consistent footer element with disclaimer or confidentiality text. Customers may also want to deploy list view command set extensions broadly across your tenancy to expose new tools.\u00a0 To solve this, global\u00a0deployment of SharePoint\u00a0Framework extensions\u00a0provides new options to broadly deploy items across your tenancy.<\/p>\n<p>Global Deployment of SharePoint Framework extensions will be offered as an experimental component in the coming weeks.<\/p>\n<p><strong>Dynamic Data<\/strong><\/p>\n<p>Web parts and extensions are designed to work on a page with other web parts. Frequently, these web parts and extensions can benefit from shared data and context \u2013 to support consistent preferences, share current user interface state, or at a minimum, avoid retrieving the same data that other components may have retrieved.<\/p>\n<p>To support this, the SharePoint Framework will support a basic event subscription and publishing model. Different web parts and extensions can subscribe to custom-designed events. When data needs to be shared from a web part or extension, it can push the data through an event to any downstream subscribers.<\/p>\n<p><strong>Adding SharePoint Pages as a Tab in Teams<\/strong><\/p>\n<p>SharePoint Pages provide team leaders with the most flexible canvas and a robust collection of web parts. Over the coming weeks, you can add rich SharePoint Pages directly within Teams channels. This makes your custom designed SharePoint Framework components available in Microsoft Teams, bringing together all of the best tools in one place. Now, as you develop new extensions for Teams, consider using SharePoint pages and SharePoint Framework.<\/p>\n<p>In addition, we\u2019re also working towards directly exposing SharePoint web parts, and their configuration options, directly as a Tab within Microsoft Teams.<\/p>\n<p>Over the coming weeks, these improvements help you get your SharePoint customizations more broadly deployed \u2013 across tenancies, and within Microsoft Teams. New developer infrastructure provides new ways to connect parts, and use additional packaging frameworks. Taken together, SharePoint Framework continues to expand with new tools to make development and deployment easier, along with new places where you can\u00a0share your work across teams.\u00a0 Stay tuned for more updates coming from SharePoint Conference North America &#8211; we look forward to your feedback!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>At Microsoft Build, we previewed several upcoming changes and improvements coming to SharePoint Framework. You\u2019ll see these changes start to release over the coming weeks, and we\u2019ll go into more detail at the upcoming SharePoint Conference \u2013 North America.\u00a0<\/p>\n","protected":false},"author":69078,"featured_media":25159,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[32],"class_list":["post-1315","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-365-developer","tag-microsoft-build"],"acf":[],"blog_post_summary":"<p>At Microsoft Build, we previewed several upcoming changes and improvements coming to SharePoint Framework. You\u2019ll see these changes start to release over the coming weeks, and we\u2019ll go into more detail at the upcoming SharePoint Conference \u2013 North America.\u00a0<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/1315","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/users\/69078"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=1315"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/1315\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/25159"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=1315"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=1315"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=1315"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}