Yarn: Some offline-cache dependancies are not being tarballed, and are being inserted into the yarn.lock as remote urls

[rjb8682]

Do you want to request a feature or report a bug?

Report a potential bug

What is the current behavior?
After walking through the steps from this guide, it seems that some dependancies are being stored into the lock file as the remote urls instead of saving them as tarballs.

If the current behavior is a bug, please provide the steps to reproduce.

> yarn config set yarn-offline-mirror ./npm-packages-offline-cache
> mv ~/.yarnrc ./
> rm -rf node_modules/ yarn.lock
> yarn install

What is the expected behavior?
All dependancies, including the dependancies dependancies, should be stored in tarball form in the specified offline-cache folder.

Please mention your node.js, yarn and operating system version.

nodejs: 4.5.0
yarn: 0.19.1
OS: MacOS 10.12.3

[rjb8682]

I noticed this ticket was made a while ago but was closed. Seems fairly similar. #318

[bestander]

I think there is still a problem with caches.
Try yarn cache clean, remove yarn.lock and try again

[rjb8682]

That did it! I appreciate the help. Hopefully this can get fixed up in the future, but at least now i have a solution if it sticks.

Thanks a ton

[elliotchi]

+1

[bestander]

I think this happens when you switch between a repo with offline cache and the one without it.
The non offline cache repo creates a global cache folder for every package in a non offline mirror compatible way.
We'll need to sort it out the sooner the better

[bestander]

The more reasons to keep yarn.lock unchanged when using offline mirror and making substitutions based on current config during install time.

[skevy]

@bestander what do you see as the next steps to resolve this issue? This is plaguing us pretty bad at Exponent -- happens every single day to some degree. Would love to help get this resolved.

[bestander]

This is at the top of our list.
@arcanis, the new core Yarn team member is working on an RFC and a fix https://github.com/yarnpkg/rfcs/pull/51.

[bestander]

This is fixed in 0.23.
Now yarn.lock contains remote URL always and the tarballs should be saved correctly