I'm currently working on an IPFS project.
While installing the dependencies - When I run
npm i libp2p-websockets
I get the following error message:
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t ssh://git#github.com/hugomrdias/pull-ws.git
npm ERR!
npm ERR! ERROR: Repository not found.
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR! exited with error code: 128
I have already setup the SSH configuration.
Do you have any idea how this could be solved?
I am also getting the same error in one of my projects after running npm install.
It is probably because hugomrdias has removed/made private the pull-ws repository.
So, far I am not sure what to do next. I will mail him with this issue.
Related
I am trying to deploy my NextJS application onto Vercel but each time at the deploy stage, I am met with these errors and the deployment will fail:
Previous build cache not available
Cloning completed: 426.52ms
Running "vercel build"
Vercel CLI 28.6.0
Installing dependencies...
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: react-typed#1.2.0
npm ERR! Found: react#18.2.0
npm ERR! node_modules/react
npm ERR! react#"18.2.0" from the root project
npm ERR! peer react#"^18.2.0" from next#13.0.5
npm ERR! node_modules/next
npm ERR! next#"13.0.5" from the root project
npm ERR! 3 more (react-dom, react-icons, styled-jsx)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react#"^16.3.0" from react-typed#1.2.0
npm ERR! node_modules/react-typed
npm ERR! react-typed#"^1.2.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: react#16.14.0
npm ERR! node_modules/react
npm ERR! peer react#"^16.3.0" from react-typed#1.2.0
npm ERR! node_modules/react-typed
npm ERR! react-typed#"^1.2.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /vercel/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /vercel/.npm/_logs/2022-12-02T16_42_09_037Z-debug-0.log
Error: Command "npm install" exited with 1
I have tried running npm install --legacy-peer-deps and tried redeploying onto Vercel, but the same issue persists. When I run this application on my localhost:3000 using npm run dev, the application renders fine. Anyone knows what I can do?
I have tried
npm install --legacy-peer-deps
and also pushing these changes onto my GitHub repository. When redeploying, the same issue still shows. I run
npm install --legacy-peer-deps
again, but this time, there are no more changes to be made.
you can override the installing command used by Vercel CLI, either by:
Going to Vercel Dashboard -> -> Settings -> General -> Scroll to Build & Development Settings and put npm install --legacy-peer-deps in Install Command
Creating vercel.json file in the root directory of your project that should contain:
// vercel.json
{
"installCommand": "npm install --legacy-peer-deps"
}
after that push and wait for deployment, it should go through this time
But I recommend looking for the cause of this issue. It seems like some dependency you're using is depending on react-typed, and the latter is not maintained anymore. It's better to seek an alternative
I use two Github platform. The public one at https://github.com and my work enterprise one https://github.work.com.
I haven't had any trouble before but I'm trying to run npm install. The project has a package.json file which contains a dependency which is references a repository in my work in git:
"my-dependency-sdk": "git+https://git#github.work.com:organization/my-dependency-sdk.git"
This is the output from the install:
npm ERR! Error while executing:
npm ERR! /usr/local/bin/git ls-remote -h -t https://git#github.work.com/:organization/my-dependency-sdk.git
npm ERR!
npm ERR! fatal: unable to access 'https://git#github.work.com/:organization/my-dependency-sdk.git/': The requested URL returned error: 400
npm ERR!
npm ERR! exited with error code: 128
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/me/.npm/_logs/2018-04-10T17_44_59_498Z-debug.log
Is it possible that the Git installation on my Mac holds some configuration that may be pointing to the public Github and the repository I'm looking for isn't there?
The URL was incorrect. It should have been:
git+https://github.work.com/organization/my-dependency-sdk.git
The format I originally used was for ssh.
I am developing a piece of software and realised that a part of it should be a separate package. Before splitting the code, I decided to try the npm link command. I followed the npm documentation to create a dummy package (exactly what the documentation describes - exports.printMsg = function(){} ...) to link to and followed the documentation about npm link. The first part (symlink to /lib/node_modules) worked perfectly. The second part failed with following error message :
npm WARN deprecated node-uuid#1.4.1: Use uuid module instead
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t http://stash.grupa.onet/scm/oacc/node04-iconv.git
npm ERR!
npm ERR! fatal: unable to access 'http://stash.grupa.onet/scm/oacc/node04-iconv.git/': Could not resolve host: stash.grupa.onet
npm ERR!
npm ERR! exited with error code: 128
npm ERR! A complete log of this run can be found in:
npm ERR! /home/lisa/.npm/_logs/2017-08-02T16_29_12_731Z-debug.log
Could you help me out, please? All I found about similar errors suggest to reboot my PC (what I did) or to upgrade npm (I am running 5.3.0).
What I don't understand is why a command that should symlink a package is trying to resolve something...
I have created the IBM Watson Natural Language Processor service and I'm trying to deploy the training application. It creates the project, clones the repository, and configures the pipeline, but gets an error during the 'Deploy to Bluemix' step.
The error is:
Cloning the 'master' branch from repo 'https://P90MSG01:3041/git/esilky/ibmwatson-nlc-groundtruth-esilky-952'
/opt/IBM/node/bin/npm -> /opt/IBM/node/lib/node_modules/npm/bin/npm-cli.js
npm ERR! Error: EACCES, mkdir '/opt/IBM/node/share/man/man3'
npm ERR! { [Error: EACCES, mkdir '/opt/IBM/node/share/man/man3']
npm ERR! errno: 3,
npm ERR! code: 'EACCES',
npm ERR! path: '/opt/IBM/node/share/man/man3' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! System Linux 3.13.0-52-generic
npm ERR! command "/opt/IBM/node/bin/node" "/opt/IBM/node/bin/npm" "install" "npm#2.14.4" "-g"
npm ERR! cwd /home/pipeline/6abb55b0-7254-4bc1-8d74-aa4550db9b1b
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! path /opt/IBM/node/share/man/man3
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, mkdir '/opt/IBM/node/share/man/man3'
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/pipeline/6abb55b0-7254-4bc1-8d74-aa4550db9b1b/npm-debug.log
npm ERR! not ok code 0
Finished: ERRORED
What needs to be done to resolve this?
Looks like your question was already answered here.
According to Patrick Wagstrom, the problem was fixed in December 7, 2015
If you try to deploy the NLC toolkit today it will work.
NLC Toolkit: https://hub.jazz.net/project/wdctools/ibmwatson-nlc-groundtruth/overview
I'm running an example from build-nodejs-npm-installation-package-scratch. Instead of uploading to npm repository I'm putting it on Github and trying to download it via npm instead. I run npm install git+https://github.com/t2wu/replaceme.git and got the following:
npm ERR! Error: ENOENT, chmod '/private/tmp/node_modules/replaceme_tim/replaceme.js'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR! <http://github.com/npm/npm/issues>
npm ERR! System Darwin 13.2.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "git+https://github.com/t2wu/replaceme.git"
npm ERR! cwd /private/tmp
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.9
npm ERR! path /private/tmp/node_modules/replaceme_tim/replaceme.js
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /private/tmp/npm-debug.log
npm ERR! not ok code 0
I have a package.json in there, I cannot figure out what is wrong.
EDIT: I can install Express OK, but I can't install my practice module
This happens due to missing permissions or unlinked files while npm was working. This topicc is also seen at github, here.
Try running with admin perms.