integration with Deno?

[d4rk0de]

[monstercr]

its beginning :)

[jasonnutter]

At this time, we are prioritizing MSAL Node for compatibility with the latest versions of Node. We may consider supporting Deno incrementally after GA. cc: @sameerag

[josh-hemphill]

In the meantime I've created a polyfilled fork and bundled into a deno package. Once official support comes, I'll be happy to have it removed/archived to prevent confusion. Should also be a good reference when going to create the official package.
https://deno.land/x/azure_msal_deno@v1.1.0
Just needed something in the meantime to get started on a couple of small tools.

[sameerag]

@EmLauber can we have this tracked internally in our backlog to evaluate if we can support it?

[josh-hemphill]

Since I started on that fork, Deno has released a Node.js compatibility layer that can be used to create a wrapper and a bundle that ultimately calls the Deno api instead of the Node.js. So that would probably make it possible to just add a single file and a CI step to add support for deno.

[jasonnutter]

Since I started on that fork, Deno has released a Node.js compatibility layer that can be used to create a wrapper and a bundle that ultimately calls the Deno api instead of the Node.js. So that would probably make it possible to just add a single file and a CI step to add support for deno.

@josh-hemphill Are you referring to this? https://deno.land/manual/node/compatibility_mode#node-compatibility-mode

[josh-hemphill]

Yep, I've had a lot of luck with it, the only significant things I've found that are still missing are the polyfills for node's raw sockets and DNS interfaces.

[jasonnutter]

@josh-hemphill Thanks. Not sure when we'll be able to prioritize this, but you are welcome to open a PR demonstrating what support for Deno would look like in MSAL Node.