How to handle native yarn binaries on multiple platforms?

I have a nodejs project with several modules, one of them (appdynamics) serving its own binary file depending on the platform / architecture of the requestor. This, combined with the fingerprint of the yarn in the lock file, creates a problem:

  • on macOS, when developing, I have one native binary
  • on Linux, when deploying, I need another native binary

Yarn does not allow this out of the box due to the above fingerprints.

Currently, the only workaround I have found is to install the code base in the Docker container and run the yarn commands from there, and then commit the lockfile changes.

Is there a better way to achieve this?

+5
source share

Source: https://habr.com/ru/post/1262534/


All Articles