node-sass: tunneling socket could not be established - sockets

This error shows up when I try to install node-sass. I need it to let work gulp protractor.
C:\Windows\system32>cd C:\Program Files (x86)\Jenkins\workspace\testnew
C:\Program Files (x86)\Jenkins\workspace\testnew>npm install node-sass
npm WARN package.json testproject#0.0.0 No repository field.
npm WARN package.json 2#0.0.1 No repository field.
-
> node-sass#2.1.1 install C:\Program Files (x86)\Jenkins\workspace\testnew\node_
modules\node-sass
> node scripts/install.js
tunneling socket could not be established, cause=socket hang up
> node-sass#2.1.1 postinstall C:\Program Files (x86)\Jenkins\workspace\testnew\n
ode_modules\node-sass
> node scripts/build.js
Does someone know how to fix this kind of error?

Related

How to use Yarn registry as Azure DevOps artifact upstream feed?

I have a mono repo in Azure DevOps that contains JavaScript packages. I use lerna for managing packages and yarn as package manager. I'm new to Azure DevOps artifacts and I want to setup yarn to be a upstream feed. I have read Use npm to store JavaScript packages in Azure DevOps Services or TFS and followed the steps. With npm seems everything works fine and after I enter npm i in my project I can see packages that sourced npm in azure artifact. But if I use yarn nothing happens. Can somebody help me?
Project .npmrc:
registry=https://pkgs.dev.azure.com/<OrganizationName>/_packaging/<OrganizationName>/npm/registry/
always-auth=true
Global .npmrc in %HOMEPATH%\.npmrc
//pkgs.dev.azure.com/<OrganizationName>/_packaging/<OrganizationName>/npm/registry/:_authToken=blahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblah
I also go to feed settings and add yarn registry as new public upstream source and move it up to be 1st upstream source. but if I enter yarn install in my project and then go to Azure artifacts and filter artifacts by source yarn nothing shown.
npm ping with that .npmrcs:
path\to\project's\package.json>npm ping
npm notice PING https://pkgs.dev.azure.com/<OrganizationName>/_packaging/<OrganizationName>/npm/registry/
npm ERR! code E404
npm ERR! 404 Not Found - GET https://pkgs.dev.azure.com/<OrganizationName>/_packaging/<OrganizationName>/npm/registry/-/ping?write=true
npm ERR! 404
npm ERR! 404 'ping' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\<UserName>\AppData\Roaming\npm-cache\_logs\2020-03-27T03_20_26_797Z-debug.log
npm ping in somewhere else:
C:\WINDOWS\system32>npm ping
npm notice PING https://registry.npmjs.org/
npm notice PONG 1.296ms
I deleted Yarn cache folder in %LOCALAPPDATA%\Yarn\Cacheand also yarn.lock file and node_modules folder in my project root and then reinstalled packages. I think problem was due to yarn.lock file. Because in yarn.lock file for each package specified registry and because I haven't package-lock.json npm works and yarn doesn't.
You can see before I delete yarn.lock file and after I reinstall package in image blow:

npm WARN deprecated browserslist#2.11.3: Browserslist 2 could fail on reading Browserslist >3.0

I'm using ionic 3 whatsapp clone github project but when i run ionic serve command got this error when i try to install appscripts Error npm WARN deprecated browserslist#2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
Uninstal Ionic and Cordova:
npm uninstall cordova ionic
Then clean cache:
npm cache clean -f
Then install ionic and cordova again:
npm install -g ionic#3.4.0
npm install -g cordova#7.0.1
Worked for me!
I had the same problem and fixed it by using the following command in the project directory:
npm install
This will install needed packages, so the project can work properly.
See also:
npm deprecated WARN for newly created app #4926
The error itself comes from the package.json file in the browserslist folder in your project.
"deprecated": "Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools."
I'm installing Laravel but get the same error.
I allowed the npm install to go all thr way through and scrolled up. There are some issues present in mine. Will possibly say something like the below.
npm WARN ajv-keywords#3.2.0 requires a peer of ajv#^6.0.0 but none is
installed. You must install peer dependencies yourself.
npm WARN img-loader#3.0.0 requires a peer of imagemin#^5.0.0 but none
is installed. You must install peer dependencies yourself. npm WARN
optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.4
(node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY:
Unsupported platform for fsevents#1.2.4: wanted
{"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
You can run npm install again if you'd like and this should give you the new errors in a more compact area.
-note: notice the commands below correspond with what is stated after "requires a peer of..."
npm i ajv
npm i imagemin#5.0.0
npm install
Not sure why, but the imagemin wouldn't work unless I specified the version.
At this point I only had one error left
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.4
(node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY:
Unsupported platform for fsevents#1.2.4: wanted
{"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
I believe this has to do with me being on a windows machine. If you get this error just force it. If anyone has a better solution at this point I'd love to hear it.
npm i -f
You could try a reset.
rm -rf node_modules
rm package-lock.json yarn.lock
npm cache clear --force
npm install
I fixed this issue by putting required binaries in the .bin folder under node_modules folder

Unable to publish Loopback application to IBM Cloud using API designer

#ibm -
I'm getting following error while trying to publish loopback application on IBM Cloud using API Designer portal. Please help me understand why is it looking into Temp folder to publish the application and how I can bypass that. I keep getting resource busy or locked issue with apiconnect toolkit.
Here's the node, npm and apiconnect toolkit version I'm using currently. Please let me know if you need any additional details.
node - v8.9.4
npm - v5.6.0
apiconnect - v5.0.8.2 (apiconnect: v2.7.111)
Error publishing runtime: Command failed: npm prune --production npm
ERR! path
C:\Users\SUNNY~1.GOE\AppData\Local\Temp\0.6717806509437265-1517290270545\project\node_modules\cryptiles\node_modules\boom\package.json.1443453620
npm ERR! code EBUSY npm ERR! errno -4082 npm ERR! syscall rename npm
ERR! EBUSY: resource busy or locked, rename
'C:\Users\SUNNY~1.GOE\AppData\Local\Temp\0.6717806509437265-1517290270545\project\node_modules\cryptiles\node_modules\boom\package.json.1443453620'
-> 'C:\Users\SUNNY~1.GOE\AppData\Local\Temp\0.6717806509437265-1517290270545\project\node_modules\cryptiles\node_modules\boom\package.json'
npm ERR! A complete log of this run can be found in: npm ERR!
C:\Sunny\npm-cache_logs\2018-01-30T05_31_21_546Z-debug.log Error ID:
a055ee2d-8232-459b-bf62-f4340837a61b
As a simple step, first run this command from cli
apic stop all
and try the publishing loopbaclk application to IBM Bluemix.
In case, this does not resolve the issue, then the problem may be due to permission issues during the installation of APIC toolkit. Uninstall the toolkit do a fresh install of toolkit using '--unsafe-perm' option with the install command to overrides the permisson issues Here is the example
sudo npm install --unsafe-perm -g apiconnect
Try the publish with the new instance of API Connect and see if it resolves the issue.

Serve error with ionic conference app

Trying to get ionic conference app (https://github.com/driftyco/ionic-conference-app) working.
ionic 2.1.13
npm version: 3.10.8
node version: 6.9.1
cordova version: 6.4.0
ionic serve -l results in the following output:
ionic-conference-app# ionic:serve C:\data\app\mkb
ionic-app-scripts serve "-l"
[13:21:16] ionic-app-scripts 0.0.44
[13:21:16] watch started ...
[13:21:16] build dev started ...
[13:21:16] clean started ...
[13:21:16] clean finished in less than 1 ms
[13:21:16] copy started ...
[13:21:16] transpile started ...
events.js:160
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE 0.0.0.0:8100
at Object.exports._errnoException (util.js:1026:11)
at exports._exceptionWithHostPort (util.js:1049:20)
at Server._listen2 (net.js:1257:14)
at listen (net.js:1293:10)
at net.js:1403:9
at _combinedTickCallback (internal/process/next_tick.js:77:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
at Module.runMain (module.js:606:11)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program >
Files\nodejs\node_modules\npm\bin\npm-cli.js" "r
" "ionic:serve" "--" "-l"
npm ERR! node v6.9.1
npm ERR! npm v3.10.8
npm ERR! code ELIFECYCLE
npm ERR! ionic-conference-app# ionic:serve: ionic-app-scripts serve "-l"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ionic-conference-app# ionic:serve script 'ionic-app-
scripts serve "-l"'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ionic-conference-app package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! ionic-app-scripts serve "-l"
npm ERR! You can get information on how to open an issue for this project with:
...
There was an error serving your Ionic application: There was an error with the spawned command: serve
Any ideas as to what has gone wrong?
Many thanks
I've just tried it and it was working for me. On the package.json, it's showing that it's using the latest rc3 ("ionic-angular": "2.0.0-rc.3-201611211919") so try to do the following:
Update your ionic CLI: npm install -g ionic
Delete your node folder and do again npm install
Now, what do you get with ionic serve ?
the error you get is
listen EADDRINUSE 0.0.0.0:8100
looks like the port 8100 is in use.
try running on a different port using
--port=8101
also you can change this value in the run.js file
The error suggests to me that the port is in use already.
In my case I closed my browser instances connected to my Ionic app and also closed down my other VS Code Ionic projects and tried running the ionic serve command again and this appeared to resolve the problem.

npm error while installing ionic dependencies

After cloning the project code from the Repository, I'm trying to install the npm to update the packages and plugins included. The command used is:
npm install
It worked well for previous clones. But now it displays the following error:
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents#1.0.12
npm WARN appname# No repository field.
npm WARN appname# No license field.
When I tried to install fsevents using --verbose, it is said that the supported OS is Darwin. But it worked in the previous clone. Why not now?
If your a Windows user:
The fsevents warning isn't a problem. It's an optional dependency and isn't needed for this to work on Windows.
But the error still displaying, in order to fix this.
Open package.json and delete the gulp-watch dependecy
Manualy remove the folder (gulp-watch) from the node_modules fordel
Unload the Project and uploaded again
The error is gone!!!
There's a issue open to fix this in .net core , but this will work untill then.