Linking local packages with yalc | Developers

Linking local packages with yalc

Estimated reading time: 2 minutes

Why use yalc?

When you work on several projects that have dependencies between each other.

Using yalc, you can use a local copy of a dependency instead of the one coming from NPM. This allows you to quickly test modifications on the dependency without having to publish a new version on NPM every time.

You may need to override some package with a local version (like @ledgerhq/cryptoassets or @ledgerhq/hw-app-mycoin) if your js bindings are not published yet.

How to use yalc?

Install it globally:

npm i yalc -g or yarn global add yalc

On the repo that is the dependency (eg. @ledgerhq/cryptoassets):

yarn install
yalc publish --push

On the repo that has the dependency (eg. @ledgerhq/ledger-live-common):

yalc add @ledgerhq/cryptoassets # Notice the difference in the package.json file after this command
yarn install

Since your build would be used locally during developemnt, you may also want those dependencies to be local and included in the published local package. Ensure the .yalc directory is included then in the package.json:


  "files": [

To stop using your local dependency repo, and revert to the original one:

yalc remove @ledgerhq/cryptoassets

Sometimes yalc’s cache get corrupted, (on Linux) you can clean it with:

rm -rfv ~/.yalc/{,.}

How to see all your current uses of yalc:

yalc installations show

Do not commit changes due to the usage of yalc as it may result in wrong behaviour.

Did you find this page helpful?

How would you improve this page for developers?

Ledger Live Setup
Getting Started
Theme Features