@koltyakov have a quick look at this when you get a chance, please. Adds adal support and teams are the big things. New doc here.

Isn't adal-angular a bit related to Angular? - Considering this fix does import * from 'angular-adal'.
Also, will this add SharePoint ADAL support (unless I'm mistaken, that still require SSL key)?

@eirikb - that is the package they published. Ideally it wouldn't be named that and would just have the core adal stuff, but that is the official adaljs package that is available. I am not sure what you mean by SPO requires keys? The below works for an app id registered with SPO permissions.

sp.setup({
    sp: {
        fetchClientFactory: () => {
            return new AdalClient(
                "ac68ea8f-79gc-47a7-a292-158c97331c66",
                "{tenant}.onmicrosoft.com",
                "https://{tenant}.sharepoint.com/_forms/spfxsinglesignon.aspx");
        },
    },
});

const r = await sp.web.get();

console.log(r);

@patrick-rodgers is that for adal and user login? I'm thinking about from nodejs, without users.

Ok, different problem. This PR is only associated with in-browser support. You can add another issue for the node stuff and we can see about adding support. Right now the adal node client is pretty basic so I am sure can be improved.

I see. Thanks! :)
I think this issue will help a lot in general, as the support is probably a lot about ensuring that the headers will correctly follow the library methods around, which will help nodejs ADAL support a lot.