Fix npm install on cloud-native branch
#16456
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![hound[bot]](https://avatars.githubusercontent.com/in/3598?s=60&v=4){kind=small}
lib/assets/javascripts/new-dashboard/pages/Data/CatalogDatasetData.vue
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TL;DR;
Just fix the
npm installscriptExplanation
The recommended Node Version for this repository is
10.15.1, which uses npm6.4.1under the hood (see.nvmrc).When trying to install dependencies directly from Git repositories, this version of NPM uses internally the git: protocol, which performs operations such as:
/usr/bin/git ls-remote -h -t git://github.com/<organization>/<repository>.gitgit clone --depth=1 -q -b master git://github.com/<organization>/<repository>.git <some-cache-directory>However, Github dropped support for this protocol a while ago, hence
npm installfails always.The less elegant, but most pragmatic solution @Josmorsot and I found during the journey is to redirect every
git:protocol request throughhttps:by modifying the NPM configuration locally