Skip to content
Discussion options

You must be logged in to vote

@DeepakMalkan this happens when you're switching between the npmjs registry and another registry such as Azure Artifacts. The easiest way to fix it is to delete the package-lock.json and run it. I'll see what we can do about making it so you won't run into this in either case.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@DeepakMalkan
Comment options

Answer selected by calebmshafer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants