JavaScript with Yarn

We support JavaScript and Yarn 1.x ("Classic") transparently. For Yarn 2+ ("Berry") support see below. 

The following Yarn features are supported:

Lockfiles Automatically detected and generated
Offline Mirror Automatically detected and updated
Private registries Automatically detected, but Depfu needs authentication details
Automatically detected and updated
Updating of Git gems   In Beta

External Registries

We support private packages on and dedicated external registries, be it SaaS registries like like Gemfury and packagecloud or self-hosted like your own NPM registry and tools like Verdaccio.

Packages from monorepos

In the JavaScript ecosystem it’s quite common to have many smaller packages, all coming from a single monorepo. Some prominent examples are React and Babel. These frameworks are split up into several individual packages, but they’re always getting released at the same time and with the same version number.

So when we encounter a new release from one of these packages, we check if the same exact version got released for the other packages from the same monorepo as well. If yes, we group them together into a single PR, that will update all packages you’re using from that group.

Yarn 2/3 ("Berry") Support

Yarn Berry support is currently in beta. It works, but does not support the full extent of the new Yarn Berry features. Notably, we currently can't update the offline cache for "Zero install" support. 

Also, our Yarn Berry support requires Yarn 3, as we're using command line options that are not available in Yarn 2. Since we do use the cached version of Yarn (in .yarn/versions), we advise you to update to Yarn 3 if possible.


An npm project with configured workspaces is automatically detected and the workspaces' package.json files are updated in the same manner as the root one. The workspaces in the subdirectories do not have to be added one by one to Depfu, in fact, doing that will probably break things.

Still need help? Contact Us Contact Us