
You can blame me for SharePoint publishing, the object, blob and output caches, taxonomy, search driven sites, and most recently #SPFX. I ride bikes a lot.
Redmond, WA
Joined October 2009
- Tweets168
- Following15
- Followers449
- Likes64
if people are having issues with the hosted workbench not working with the 1.9 release of #SPFX, can you go to github.com/SharePoint/sp-dev… ? Trying to get a repro to diagnose, but not having much luck.
If you are using #SPFx and are running into an issue around npm not finding flatmap-stream / event-stream, you'll need to delete your shrinkwrap / package-lock / etc. file and reinstall. A clean / new 1.7.0 solution isn't picking up a dependency on the recently removed package.
The issue with #SPFx and app-pages / teams tabs -> SharePoint is fixed and rolled. You should be good to try it out now. Sorry for the hiccup. @vesajuvonen should post something so that everyone else sees it.
If your #spfx solution has errors that mention sp-client-preview, chances are you are using an old (beta, not released for production, deprecated, removed) reference to MsGraphClient from sp-client-preview. You should be referencing it from production ready location in sp-http.
#spfx 1.7 is out. github.com/SharePoint/sp-dev…
GA of Dynamic Data and SP2019 support, previews of SPFx in Teams, Teams in SP, domain isolated webparts and realtime library change notifications.
For people experiencing issues with #SPFX placeholders recently, please see the following post - github.com/SharePoint/sp-dev…
We've rolled back a recent build to double check there are no other issues, but if you are still affected by this, post here - github.com/SharePoint/sp-dev…
#SPFX 1.6.0 is out. Web API and tenant wide extensions public release!
If you are having difficulty migrating to 1.5.0 of #SPFX, the release notes have an updated section - github.com/SharePoint/sp-dev…
Let us know here or in the issues list (github.com/SharePoint/sp-dev…) if there are problems.
Reminder for people trying out #SPFX 1.5. You need to use --plusbeta with the new generator to get the beta APIs, otherwise only public released APIs will be present. github.com/SharePoint/sp-dev…
The update to the 1.3.2 of the #SPFX yeoman generator has no new features. It fixes a bug in react-based on-prem targeted webparts.
Might be missing from the docs, as it didn't jump out at me. SP2016 FP2 #SPFX solutions should use 1.0 of the yeoman generator for now.
Fixed the issue running the 1.0.0 yeoman #spfx generator. If you ran this recently, delete node modules and run "npm install".
We're aware of issues running the 1.0 version of the #spfx yeoman generator. Working on a solution and will update soon.
3
Short document on how #SPFX deals with loading versions of the framework. github.com/SharePoint/sp-dev…
You can provision SharePoint content in your #SPFX GA solution. Here are some pointers on how to do this - github.com/SharePoint/sp-dev…
#SPFX GA!!! Dev release notes are here - github.com/SharePoint/sp-dev…
Here is how to extend WebPack configuration in #spfx RC0 - github.com/SharePoint/sp-dev… . I think @StfBauer was asking about this a while ago.