[keytar] Does @azure/identity can not run on different platform with build-time platform.

• Package Name: @azure/identity
• Package Version: 1.3.0
• Operating system: win

Hi, I am creating this issue to ask whether @azure/identity can not run on different platform with the build-time machine.

We notice that @azure/identity has a keytar dependency. When we build @azure/identity on one machine (for example, x86), and run it on another machine (say ia32), since keytar is not pre-built for ia32, it will try to re-build based on the new platform, and fail during rebuild.

So, we are asking whether @azure/identity is supposed to be run on exactly the same environment (node version / arch platform) with the build-time environment due to keytar.

Thanks!

[witemple-msft]

@dilin-MS , @azure/identity 1.3.0 only uses keytar for the VisualStudioCodeCredential. If you aren’t using that credential, then you should be able to ignore the keytar depdendency. We have a feature goal for Identity 2.0 to remove this dependency entirely, as @sadasant mentioned. If you’re using VisualStudioCodeCredential, then yes, npm install needs to be run on a machine with the same CPU architecture, operating system, and node version as the deployment target machine.

[sadasant]

@dilin-MS We’ll be releasing v2 officially in a couple of months. In the mean time, you could try our beta version, but keep in mind that it might change: https://www.npmjs.com/package/@azure/identity/v/2.0.0-beta.4