Are you getting 404's?


#1

Dear Bit Developers,

Due to the compromised version of eslint-scope that was released earlier today, we have decided to take the same course of action as NPM and invalidate all Bit tokens issued before 2018-07-12, eliminating the possibility of compromised tokens.

These precaution measures were taken to ensure your safety, as Bit leverages the .npmrc file to store its token for accessing the @bit node module registry.

To generate a new token, please open a terminal application and run

bit logout
bit login

If you use npm/Yarn to install components from the @bit node package registry, you should open a terminal application and run:

npm login --registry=https://node.bitsrc.io --scope=@bit

For additional information please refer to npm and eslint’s postmortems:

We apologize for the inconvenience.


#2

#3

#4