Do i need to commit .yarn/releases folder to my repo?

Do you want to request a feature or report a bug?
Feature (i think)
I believe i need to commit the full .yarn/releases folder into the repository for others to use. This means that a full build of yarn is added to my repo. It would be much more usable if the required release is automatically downloaded if it doesn’t exist.

What is the current behavior?
Yarn crashes if the required version is not installed

module.js:549
    throw err;
    ^

Error: Cannot find module '/path/to/repository/.yarn/releases/yarn-1.19.2.js'
    at Function.Module._resolveFilename (module.js:547:15)
    at Function.Module._load (module.js:474:25)
    at Function.Module.runMain (module.js:693:10)
    at startup (bootstrap_node.js:188:16)
    at bootstrap_node.js:609:3

What is the expected behavior?
To install the specified yarn version if the file is not found.

Author: Fantashit

1 thought on “Do i need to commit .yarn/releases folder to my repo?

  1. So far the answer seems to be yes. It becomes a hard-dependency of the project to run or even install as you intend.

Comments are closed.