-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git LFS not supported #1337
Comments
Any news? |
This does not work git git+ssh dependencies, which seems weird to me since, as far as I understand, yarn caches the full git repo with git clone for such dependencies. |
Any update on this? |
Pretty sure LFS support has been implemented for some time (modulo bugs), but one way this issue can still manifest is with stale yarn cache entries. If at some point the cache was populated prior to installing/configuring git lfs on your client, then it will have saved the LFS reference pointer file instead of the actual binary. Try cleaning the yarn cache before running yarn install. |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Installed packages that depend on Git LFS will fail. Ie. if the package has a postinstall script that unzips a large tar file, that is stored via Git LFS then the tar command will fail since it's not an actual tar file but a text file with a LFS reference.
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
tar file is fetched via git-lfs, postinstall script runs, and tar succeeds.
Please mention your node.js, yarn and operating system version.
node: v6.9.1
yarn: v0.16.1
macOS: 10.12 (16A323)
This issue seems related to these NPM issues:
npm/npm#10857
npm/npm#11151
The text was updated successfully, but these errors were encountered: