Im getting the following error when running running npx playwright codegen in VScode without internet access. I believe I have all extensions installed.
[~home]$ npx playwright codegen
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! network request to https://registry.npmjs.org/playwright failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! A complete log of this run can be found in:
npm ERR! /nfsshare/home/dvamosi/.npm/_logs/2023-01-26T20_02_26_465Z-debug.log
Install for [ 'playwright#latest' ] failed with code 1
im just looking to record a playwright file on RHEL without internet access
Related
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.
I'm building app in Flutter. I have connected Strapi with Mongodb Atlas.
Everything was fine until suddenly I'm getting this kind of error:
[2020-08-03T17:03:26.651Z] debug ⛔️ Server wasn't able to start properly.
[2020-08-03T17:03:26.652Z] error Error connecting to the Mongo database. Server selection timed out
after 30000 ms
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! server#0.1.0 develop: `strapi develop`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the server#0.1.0 develop script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
My cluster is connected and I know no idea what could go wrong.
Any idea what should I do?
Apparently my ip has changed. So what i had to do is to add in mongodb atlas my new ip.
In my Cluster -> SECURITY -> Netwrok Access - ADD IP ADDRESS.
And thats its
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...
MacBooks-MacBook-Pro:~ Apple$ sudo npm install -g ionic
Password:
npm ERR! network tunneling socket could not be established, cause=getaddrinfo ENOTFOUND
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! System Darwin 13.4.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "ionic"
npm ERR! cwd /Users/Apple
npm ERR! node -v v0.10.36
npm ERR! npm -v 1.4.28
npm ERR! code ECONNRESET
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/Apple/npm-debug.log
npm ERR! not ok code 0
Try installing without sudo
npm install -g ionic
If that does not help there is an existing Github issue about proxies:
https://github.com/npm/npm/issues/3354
You might also try this Stack Overflow question:
Is there a way to make npm install (the command) to work behind proxy?
We're currently using Nexus 2.10, and have successfully used it as a repo for npm.
Building locally through this proxy/mirror works fine, but when trying to run npm install on Bamboo (which doesn't have internet access), it fails, as some dependency tries to reach GitHub to download something, which fails.
error 06-feb-2015 13:29:29 npm http 200 https://nexus.shdir.no/content/groups/npm-all/mkdirp/-/mkdirp-0.3.0.tgz
error 06-feb-2015 13:29:30 npm http GET https://nexus.shdir.no/content/groups/npm-all/formidable
error 06-feb-2015 13:29:30 npm http 200 https://nexus.shdir.no/content/groups/npm-all/formidable
error 06-feb-2015 13:29:45 npm ERR! fetch failed https://github.com/rase-/node-XMLHttpRequest/archive/a6b6f2.tar.gz
error 06-feb-2015 13:29:55 npm http GET https://github.com/rase-/node-XMLHttpRequest/archive/a6b6f2.tar.gz
error 06-feb-2015 13:30:16 npm ERR! fetch failed https://github.com/rase-/node-XMLHttpRequest/archive/a6b6f2.tar.gz
error 06-feb-2015 13:31:16 npm http GET https://github.com/rase-/node-XMLHttpRequest/archive/a6b6f2.tar.gz
error 06-feb-2015 13:31:37 npm ERR! fetch failed https://github.com/rase-/node-XMLHttpRequest/archive/a6b6f2.tar.gz
error 06-feb-2015 13:31:38 npm ERR! network connect ETIMEDOUT
error 06-feb-2015 13:31:38 npm ERR! network This is most likely not a problem with npm itself
error 06-feb-2015 13:31:38 npm ERR! network and is related to network connectivity.
error 06-feb-2015 13:31:38 npm ERR! network In most cases you are behind a proxy or have bad network settings.
error 06-feb-2015 13:31:38 npm ERR! network
error 06-feb-2015 13:31:38 npm ERR! network If you are behind a proxy, please make sure that the
error 06-feb-2015 13:31:38 npm ERR! network 'proxy' config is set properly. See: 'npm help config'
error 06-feb-2015 13:31:38
error 06-feb-2015 13:31:38 npm ERR! System Windows_NT 6.1.7601
error 06-feb-2015 13:31:38 npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
error 06-feb-2015 13:31:38 npm ERR! cwd E:\bamboo\UTV-FP-JOB1\code
error 06-feb-2015 13:31:38 npm ERR! node -v v0.10.17
error 06-feb-2015 13:31:38 npm ERR! npm -v 1.3.8
error 06-feb-2015 13:31:38 npm ERR! syscall connect
error 06-feb-2015 13:31:38 npm ERR! code ETIMEDOUT
error 06-feb-2015 13:31:38 npm ERR! errno ETIMEDOUT
How would I go about this problem? Do I have to add every repo from github/bitbucket to Nexus?
We solved the problem by downloading the binaries manually, and adding them to our Apache server. Won't be fun when updating dependencies, but shouldn't be too bad. Only 3 files.
I'd be happy to use a better solution, if anyone knows of one.
You have to make Nexus available to your Bamboo server and configure npm there just like you did on your workstation. Depending on where Bamboo and Nexus are installed in terms of network topology that might require different steps.
Ideally your repository manager and your CI server are co-located and a high performance connection to each other. This allows for fast downloads of proxied packages as well fast deployments.
You can for example make your Nexus available on the public internet and lock it down to allow only authenticated access and then use it like that from Bamboo.