Bit v1.0: Upgrade Notes

Bit is now available in version 1.0.0. This version is a major release that includes a few changes that require your attention.

Update your Bit version by running the following command:

$npx @teambit/bvm upgrade

Copied

Verify that you're running version 1.0.0 by running the following command:

$bit -v

Copied

bit.cloud's package registry has now changed from https://node.bit.cloud to https://node-registry.bit.cloud. While the old registry is still supported, we recommend migrating to the new one.

To do so, you will need to delete your workspace's lock file and run the installation again. In addition to that, any .npmrc file that points to node.bit.cloud (in your CI server or local machine) should be updated to node-registry.bit.cloud.

For example, the following .npmrc file will need to be updated from:

To the following:

To learn more about configuring your npm client to work with bit.cloud, see configuring bit.cloud in your NPM config.

Version 1.0.0 uses Ripple CI as the default CI for components builds. Components are built in the cloud after they've been exported and not when they are snapped.

If your automation flow uses bit tag --soft and bit tag --persist combo, it is still supported and you do not need to make any changes.

To snap (or 'tag') components and run their build locally, use the --build option:

$bit snap --build

Copied

$bit tag --build

Copied

To opt out of Ripple CI, and permanently run your builds locally, run the following command:

$bit config set force_local_build true

Copied

Alternatively, set the following env var:

$export BIT_CONFIG_FORCE_LOCAL_BUILD=true

Copied

Running bit build will always build your components locally.