Node_modules caching is somehow missing most of the dependencies

Archive Tooling Issues
, ,
1

Hi there,

As mentioned in this topic, node_module caching on Bitrise doesn’t work as expected. Yarn step doesn’t cache node_modules

I use the official Run yarn command workflow recipe step and set caching to true. However, I got ➤ YN0013: │ 24 packages were already cached, 3872 had to be fetched. It just downloads each dependency from scratch even though no code change in delta.

Besides that, it doesn’t seem like the Android Build step has built-in caching as it is stated in the documentation.

2

Another weird thing that happens using the pull/push cache step is to fail the workflow altogether because the CI can’t find some file in its vagrant instance. This is reproducible when the Run yarn command is kicked off for the first time for the project. Here is the output:

➤ YN0000: ┌ Link step
➤ YN0001: │ Error: While cloning /Users/vagrant/git/packages/shared/node_modules/jest -> /Users/vagrant/git/packages/bonsai/node_modules/jest ENOENT: no such file or directory, scandir '/Users/vagrant/git/packages/shared/node_modules/jest'
➤ YN0000: └ Completed in 7s 521ms
3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.