Publish JS parser using system identity

[praveenkuttappan]

Publish JS parser using system identity

[github-actions]

Hi @praveenkuttappan. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

[github-actions]

Hi @praveenkuttappan. Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing /reopen if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the no-recent-activity label; otherwise, this is likely to be closed again with the next cleanup pass.

[praveenkuttappan]

Fixes #9694

[praveenkuttappan]

@chidozieononiwu It still fails when publishing even after authenticating. I am not sure if this is because a package already exists. Npm sometimes fails with incorrect error message so we might have to try publishing a package version that doesn't exists.

[scbedd]

@praveenkuttappan @benbp it is working when invokingnpm publish in the working directory with the authed .npmrc. The only reason the latest build is failed is because we already published the version in this PR.

I did try to update the user .npmrc, and keep using the npm task (assuming that the user .npmrc was being used for auth), but nothing I tried with that worked.

[praveenkuttappan]

Thanks a lot @scbedd for this change.