git:// address in yarn.lock file makes in hard to build project
See original GitHub issueDescribe the bug In yarn.lock file you are referencing a repository with the git scheme and get the following error when trying to run yarn command.
➜ storybook git:(98f3e2c6d) yarn install yarn install v1.19.0 [1/5] Validating package.json... [2/5] Resolving packages... [3/5] Fetching packages... error Command failed. Exit code: 128
Command: git
Arguments: ls-remote --tags --heads git://github.com/CharlesMangwa/simple-markdown.git
Directory: /mnt/c/Source/github/storybook
Output:
fatal: unable to connect to github.com:
github.com[0: 140.82.118.4]: errno=Connection refused
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
From
simple-markdown "git://github.com/CharlesMangwa/simple-markdown.git"
To
simple-markdown "https://github.com/CharlesMangwa/simple-markdown.git"
Allows me to complete the yarn command.
To Reproduce Steps to reproduce the behavior:
- Clone repo
- type
yarn
Expected behavior yarn command to finish
Screenshots If applicable, add screenshots to help explain your problem.
Code snippets If applicable, add code samples to help explain your problem.
System:
Environment Info:
System:
OS: Linux 4.4 Ubuntu 18.04.3 LTS (Bionic Beaver)
CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Binaries:
Node: 10.16.3 - ~/.nvm/versions/node/v10.16.3/bin/node
Yarn: 1.19.0 - ~/.nvm/versions/node/v10.16.3/bin/yarn
npm: 6.9.0 - ~/.nvm/versions/node/v10.16.3/bin/npm
npmPackages:
@storybook/eslint-config-storybook: ^2.0.0 => 2.0.0
@storybook/linter-config: ^2.0.0 => 2.0.0
Additional context Add any other context about the problem here.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
How do you resolve Git conflicts in yarn.lock - Stack Overflow
First solve the conflict in package. json manually, then just run this: $ yarn install yarn install v1.
Read more >Why is my Node.js build failing because of conflicting lock files?
This issue commonly occurs when your application uses npm or yarn, and someone uses the other tool to install a package and checks...
Read more >Configuration options | Yarn - Package Manager
List of all the configuration option for Yarn (yarnrc files)
Read more >Managing yarn.lock Efficiently - Adobe Tech Blog
In the last blog, we saw how important lock files are, ... As developers, our responsibility is to make sure our project doesn't...
Read more >Yarn vs npm: Everything You Need to Know - SitePoint
Modern web development is virtually impossible without a package manager. ... It also generate a yarn.lock file that makes sharing and exact ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have same issue.
Package just need to be released https://github.com/CharlesMangwa/react-native-simple-markdown/blob/next/package.json#L22
Hey there, it’s me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook!