{"id":3300,"date":"2019-08-28T18:58:48","date_gmt":"2019-08-29T01:58:48","guid":{"rendered":"https:\/\/developer.microsoft.com\/en-us\/office\/blogs\/?p=3300"},"modified":"2019-08-28T18:58:48","modified_gmt":"2019-08-29T01:58:48","slug":"microsoft-graph-sdk-for-javascript-2-0-0","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/microsoft-graph-sdk-for-javascript-2-0-0\/","title":{"rendered":"Microsoft Graph SDK for JavaScript – 2.0.0"},"content":{"rendered":"

We are excited to announce a new release<\/a> of our JavaScript SDK 2.0.0 for Microsoft Graph. The version is updated to 2.0.0 because it contains a number of breaking changes. However, making the necessary changes to adopt this version should not be significant. More details can be found in our migration guide<\/a>.<\/p>\n

Removed polyfills<\/h3>\n

In the past our library has included polyfills for fetch<\/code> and promise<\/code>. However, doing so adds to the size of our library and many of our customers do not need these polyfills due to their target platform or the fact they already include them in their application. We have now removed the polyfills for fetch<\/code> and promise<\/code>. Developers who do still need the polyfills will need to include them explicitly.<\/p>\n

New minified files<\/h3>\n

Previously we shipped two different bundles, graph-js-sdk-web.js<\/code> and graph-js-sdk-core.js<\/code>, with and without dependencies bundled. These files are no longer available. Now, a new file named graph-js-sdk.js<\/code> will be shipped for use in any kind of application and can simply be referenced via a script tag. For developers building libraries that want to include the SDK, it is now available as an ES module in the graph-es-sdk.js<\/code> file.<\/p>\n

Getting Raw Response<\/h3>\n

In the past, if you wanted to get the raw HTTP response back it was necessary to pass a callback in the get(), put(), post(),etc method. The implementation of this approach was causing issues for node.js applications. To resolve this and provide a more consistent experience, we introduced a new ResponseType<\/code>. Returning raw responses is now as simple as:<\/p>\n

client\n    .api('\/me')\n    .responseType(ResponseType.RAW)\n    .get((err, rawResponse) => {\n        console.log(rawResponse);\n    });\n<\/code><\/pre>\n
Changes to the Authentication Provider<\/h3>\n
In anticipation for support of more authentication flows, the MSALAuthenticationProvider<\/code> class has been renamed to ImplicitMSALAuthenticationProvider<\/code>.<\/p>\n
In order to create an instance of ImplicitMSALAuthenticationProvider<\/code> you now must pass an instance of MSAL’s UserAgentApplication<\/code> and MSALAuthenticationProviderOptions<\/code>. This brings consistency with the SDKs from other platforms and ensures that an application can have easy access to the UserAgentApplication<\/code> to interact with it directly. Be aware that in the v1.0.0 release of MSAL.js there were breaking changes to the way UserAgentApplication<\/code> is created.<\/p>\n
Default Content-Type for PUT method<\/h3>\n
Some users reported confusion when trying to perform PUT calls that would fail due to missing or invalid Content-Type<\/code> header. To minimize these issues we decided to default the Content-Type<\/code> to application\/json<\/code> as this is the most common case. When trying to PUT a payload other than JSON, simply use the .header<\/code> method to change the Content-Type.<\/p>\n
Definitely Typed<\/h3>\n
For developers who only need to use the Typescript types for the request and response models we have now published these types to the Definitely Typed repository under the name microsoft-graph<\/code>.<\/p>\n
Feedback<\/h3>\n
Thank you to all the community members who continue to provide us feedback on this library. We encourage you to go and upgrade to this new version of our Graph JavaScript API. You can follow these links for installation instructions, release notes<\/a> and npm packages<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
We are excited to announce a new release<\/a> of our JavaScript SDK 2.0.0 for Microsoft Graph.<\/p>\n","protected":false},"author":69114,"featured_media":25159,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3],"tags":[],"class_list":["post-3300","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-graph"],"acf":[],"blog_post_summary":"
We are excited to announce a new release<\/a> of our JavaScript SDK 2.0.0 for Microsoft Graph.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/3300","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\/69114"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=3300"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/3300\/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=3300"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=3300"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=3300"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}