Microsoft 365 Community Community Demos, 14 Sep 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Microsoft Graph JavaScript SDK Updates

Description

In this 6-minute developer-focused demo – Roina Ochieng orients viewers on a non-PowerShell, cross platform alternative command line experience for accessing the Graph. The development journey – today - Public Preview v0.1.6 (Windows) to GA (Win, Mac, Linux, Docker). CLI demo - get the CLI msi from the Repo, install it, help to see commands, authenticate against Graph, use scopes, list users in tenant, specify output parameters – select or JsonPath queries. This PnP Community demo is taken from the weekly Microsoft 365 Platform Community call recorded on September 14, 2021.

Demo Presenter: Roina Ochieng (Microsoft) | @roinochieng

Supporting materials:
• Repo/Library - Microsoft Graph JavaScript Client Library | https://github.com/microsoftgraph/msgraph-sdk-javascript
• Guide - Microsoft Graph JavaScript SDK V3.0 Upgrade Guide | https://github.com/microsoftgraph/msgraph-sdk-javascript/wiki/Microsoft-Graph-JavaScript-SDK-V3.0-Upgrade-Guide
• Blog post - Microsoft Graph JavaScript SDK 3.0.0 is now generally available | https://developer.microsoft.com/microsoft-365/blogs/microsoft-graph-javascript-sdk-3-0-0-is-now-generally-available/

Learn more:
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp/videos

A

My name is royna. I am one of the pms on the microsoft graph developer experience team. I work with the engineers who are behind the jayhawks sdk, and so I want to start off by saying a big thanks to all our contributors on the javascript sdk.

A

It's been a long journey and we're really just trying to make changes to make sure that, if you're using this javascript sdk, but you are having the best possible experience, so we um put the v three in ga of the javascript sdk in mid august and thank you so much for the traction already on moving up from 2.1 um and we do have a couple of changes that I thought would be important for your contributors here. To keep in mind. This new version has breaking changes.

A

We have the node.js 10, lps or higher requirement, and we also have the update to type script for point whatever. It is right now um so yeah if you are bumping up, these are breaking changes that you're going to need to consider and also we've made a couple of enhancements on the large file upload tasks. We're now allowing you to upload a lot bigger files. We have added, also new, update new classes to allow you to manage the upload process even better. We also removed the timeout option from the fetch options, um interface and we've.

A

Given you an alternative way to cancel the request by passing a signal here. um This is the upgrade guide it can be found on our github repo. We also did a blog post on the m365 developer blog that I will share on the link after my presentation that can give you a much uh greater detail of what these enhancements mean to your workflow and if you do need any help, transitioning or if you are using any of the tool chains that are currently exposing the javascript sdk but you're in the older versions.

A

We are trying to enable you to um move to the newer versions of the javascript sdk, because there's a lot more cooler functionalities that you can leverage on, and we also are hoping to collaborate with, like the sharepoint file exchange team and the teams, one two to enable you to bring your own to use whatever version of the javascript sdk um that you would want to in in your workflows, if you're using any of those tool chains. So that's something that's currently under the arts and should be expected as an enhancement coming soon.

A

If this is beneficial to you, please uh reach out, let us know- and we can also just like collaborate on the kind of scenarios you're using the javascript and those two chains for and yeah we'd love your feedback on that. We also removed the graph es sdk and it's being shipped now as the graft js sdk dot js. So there's that change. That's also there and then there's also few enhancements on some older parts. I'm not gonna go into that uh yeah and so the other big one is authentication.

A

We are introducing support for the azure identity, token credentials. In version 3.0 and um yeah, because we understand that there is a gap in the browser, authentication, we've also added we've. Also, given you an authentication package that can allow you to use the m cell browser auth. So that's also um available if um based off of the current gaps of the token credentials implementation right now we have deprecated implicit, msl auth provider because of the flow, the implicit authorization for not being recommended any longer. So that's a huge deprecation to keep in mind.

A

um We are still trying to restructure our authentication options on the javascript sdk. So please look out for changes on that and just an open call to anybody who is using the javascript sdk who is having challenges moving from one of the older versions. Our data should address that a lot of the javascript sdk users are currently still on one point or we'd love to know um what your experience is and what the blockers are to transitioning, so that we can make that a lot easier for you.

A

um I will share the relevant links for our repo if you do have any feedback. Our repo is here with updated documentation, and you can also always just submit an issue and we'll get back to you and also leverage our github discussions and microsoft. Q. A if you have any questions in regards to this and yeah. I will share the relevant links too.

A

That's pretty much it for me visa. uh Let me see if there's any questions on the chat.

B

Thanks trina, there was a chance. uh I think that was raised two times related on alignments with sharepoint framework uh and that version with the typescript and microsoft craft toolkit. So it might be that we need to take some of this offline, but any any updates on that. Can you comment or.

A

Yeah, yes, um I can't comment that work on alignment with um sharepoint will be commencing this second quarter of our planning process, so we'd already scoped out what needs to be done and you're already in conversations and making that happen, so we will be seeing um good progress on that front um from um the end of september. Moving forward.

B

Cool that was all what was spending in a chat. Thank you, royna on this one.