Property does not exist on type: Why does TypeScript complain while JavaScript doesn't?

Question

In the following code

import { useMsal } from "@azure/msal-react";

function ProfileContent() {
    const { instance, accounts } = useMsal();

    const name = accounts[0] && accounts[0].name;

JavaScript has no problem with this, and the code works as expected. But when I make this a TypeScript file, I get errors that

Property 'name' does not exist on type 'Partial<Pick<AccountInfo, "homeAccountId" | "localAccountId" | "username">>

What has so drastically changed to the point that TypeScript believes the property within the library doesn't even exist?

You might be accessing the accounts object outside of the msal-react context. Here is some documentation for that particular NPM library: github.com/AzureAD/microsoft-authentication-library-for-js/tree/… — Chris
– Chris, Commented Jun 14, 2021 at 3:36

Calvin · Accepted Answer · 2021-06-14 03:44:54Z

1

Browsing through the source code, it looks like they might have used the wrong type in IMsalContext. There's a commit on the dev branch with the message "Fix accounts type".

Here is the current released version, the dev branch version, the pull request, and the associated issue.

edited Jun 14, 2021 at 3:44

answered Jun 14, 2021 at 3:38

Calvin

5033 silver badges7 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

8protons Over a year ago

Confirmed with the dev team that this was/is a bug. Thanks!

Collectives™ on Stack Overflow

Property does not exist on type: Why does TypeScript complain while JavaScript doesn't?

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related