Unable to npm install

[connor4312]

1. Clone the pakage
2. Try to npm install
3. This error happens, in spite of being logged in:

npm ERR! code E401
npm ERR! Unable to authenticate, your authentication token seems to be invalid.
npm ERR! To correct this please trying logging in again with:
npm ERR!     npm login

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/connor/.npm/_logs/2021-10-08T17_05_39_275Z-debug.log

It looks like there are references to mscomdev.pkgs.visualstudio.com in the package-lock.json. This prevents anyone who isn't authenticated and set up to that package feed from being able to contribute. All dependencies are public, so we should be able to just reference the public npm registry.

[hawkticehurst]

Oh boy! Could've sworn I had cleared package-lock the other day but regardless thank you for the catch!! I'll update it right now.

[hawkticehurst]

Just dropping in to give an update that the original issue has been fixed, but we've run into a new bug that is making our build command fail. Working to get it fixed asap and then will push all the changes.

[connor4312]

Thanks!

[hawkticehurst]

Another quick update is the bug seems like it might be related to an issue with fast foundation and a build tool both packages use called api-extractor.

Details aside, I'll be reaching out to someone on the fast team to see if they might have some insights and will hopefully have this issue resolved by Monday since I don't expect to get much of a response on a Friday at 4pm 😅

[connor4312]

fwiw I was able to get a successful install just by deleting package-lock.json and running npm install.

[hawkticehurst]

Yep, that's what worked for us too! However, the issue we ran into is when you try to run npm run build the build now fails and so I'd rather not push changes that result in not being able to build the package 😅.

[hawkticehurst]

Regardless, I'm happy to hear you found the same solution in the meantime!