Run bvm upgrade to get the latest stable version of Bit. See Install experimental releases to try out the latest experimental features.

You can now see which components use a specific dependency. This is useful when you want to know which components are affected by a bug in a dependency, or which components use a specific version of a dependency.

Run the bit why command with the component ID or package name of the dependency you want to check:

$bit why @teambit/community.ui.text-tooltip

Copied

The output lists the components that use the dependency, as well as the path to the component directory of dependent components maintained in the workspace:

Specify a version to look for a specific version of the dependency. For example bit why @teambit/community.ui.text-tooltip@0.0.3.

Bit enables you to test locally maintained components in a non-Bit project by generating symlinks to them, from your project's node_modules directory.

For example, the following command generates symlinks to Bit components from the current Bit workspace to the node_modules directory of 'my-non-bit-project':

$bit link --target path/to/my-non-bit-project

Copied

To learn more read the Linking workspaces docs.

We've created a suite of scripts to help you integrate Bit with your existing CI system. You can suggest new component versions on a separate git branch, build and test them in isolation, make them available for consumption for other projects in a temporary Bit lane, and release them only when the branch is merged to master.

Github Actions

Azure Devops

GitLab CI

Jenkins

Circle CI

Bash scripts (Other CIs)

The default Angular env now supports Angular v17!

You can create a new workspace with Angular v17 by using the following command:

$bit new angular my-workspace --env bitdev.angular/angular-env

Copied

If you were using the default Angular env and want to continue using v16, you can replace it with:

$bit envs replace bitdev.angular/angular-env bitdev.angular/envs/angular-v16-env

Copied

We've updated our lit env to lit v3.

If you're using a custom env that extends the lit base env, run the following to update it to the latest version of the lit base env:

$bit update @teambit.web-components/lit --yes

Copied

If your components use the base lit env directly then run the following to update to the latest version of the lit base env:

$bit envs update teambit.web-components/lit

Copied

The bulk of changes in v3 are internal to lit, so it's a relatively non-breaking new version and most lit components wont need to be changed at all after upgrading. If you run into issues after the upgrade please check the lit v3 release notes above and/or get in touch with bit.