Not Able to Install Angular CLI - javascript

I am getting below error while installing angular cli.
Please help me
C:\Users\A737539>npm install -g #angular/cli#6.1.3
npm ERR! code E502
npm ERR! 502 Parent proxy unreacheable: #angular/cli#6.1.3
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\A737539\AppData\Roaming\npm-cache\_logs\2018-11-21T09_33_42_128Z-debug.log
Thanks,
Pushkar

Here is how you can get npm work when on a proxy network :
create a .npmrc file with below fields :
registry= //local artifactory site if any - remove if not
strict-ssl=false
cache=.\npmcache
prefix=.\npm
package-lock=false
loglevel=verbose
proxy= http://domain\username:password#servername:port/
https-proxy= http://domain\username:password#servername:port/
unsafe-perm=true
sass-binary-site= // if any local binary site is present - remove if not
Now place this file into mentioned location : C:\Users\A737539> and then
run npm install command it will work.
Once done , You can place this file inside repository (any new app created using cli) so that each time you don't have to set proxies manually.

Related

why i can not create a new react app with npm?

im going to create a new react app with npm , but it dos'nt work and i have too many errors each time i try
can someone help me please?:(
i entered this line in cmd
npx create-react-app my-app
and the errors :
npm ERR! code ECONNRESET
npm ERR! syscall read
npm ERR! errno -4077
npm ERR! network read ECONNRESET
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! C:\Users\sobha\AppData\Local\npm-cache\_logs\2022-11-29T11_57_33_191Z-debug-0.log
Aborting installation.
npm install --no-audit --save --save-exact --loglevel error react react-dom react-scripts cra-template has failed.
Deleting generated file... node_modules
Deleting generated file... package.json
Deleting my-app/ from C:\Users\sobha\Desktop\react
Done.
Firstly Check your network connection and then
npm cache clean --force
npm create react-app
The problem could easily be you are being blocked to that website by your ISP's or Company's firewall/proxy. Using the above method is quicker and easier but it's also insecure as it doesnt verify you are connected to the right website. To check if you are being blocked simply go to registry.npmjs.org in your browser. You should get some text back.
Option 1
Try this:
npm config set registry http://registry.npmjs.org/
so that npm requests for http url instead of https.
and then try the same npx create-react-app my-app command.
Option 2
You may also want to check your NPM proxy settings and perhaps remove it.
npm config get proxy
npm config rm proxy
npm config rm https-proxy

ENOLOCK npm ERR! Error while running npm audit fix

I am trying to install GLOBALLY a package with npm from my home directory. After the install has completed, it indicates vulnerabilities. Upon trying to run npm audit fix, I obtain the following error.
npm ERR! code ENOLOCK npm ERR! audit This command requires an existing
lockfile. npm ERR! audit Try creating one first with: npm i
--package-lock-only npm ERR! audit Original error: loadVirtual requires existing shrinkwrap file
I understand that the error asks me to run npm i --package-lock-only, but in which directory should I be creating this file? Running the command without specifying a path does not work. I have also tried to create the file in the directory where the package was installed, but that has also not solved the issue. Also, why isn't this file present to start with?
npm audit fix is intended to fix vulnerabilities with the dependencies of your own project. Projects do have a package-lock.json file.
It is not intended for globally installed packages. If there are vulnerabilities with packages from others, they need to be fixed by the package maintainer in a new release. You can then update to this new release.
BTW, you should not use globally installed packages. Use npx instead.

Unable to install a npm package and dependency

I'm trying to adapt an external API named cric-live into my node application for displaying cricket scores in my application. When I try to install the dependency, it shows an error as below
PS F:\Node Express\NodeJS\cric api> npm i cric-live
npm ERR! Unexpected end of JSON input while parsing near '...":"request-promise","'
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Thiluxan\AppData\Roaming\npm-cache\_logs\2020-07-01T04_51_42_400Z-debug.log
This is the source link for the dependency I'm trying to install
https://www.npmjs.com/package/cric-live?activeTab=readme
Your npm cache maybe busted so I would say run this code first and try installing the package again
npm cache clean --force

error: this is probably not a problem with npm. This is likely additonal logging output above

C:\Users\Jorge\Desktop\space-xplorer>npm install
node-sass#4.11.0 install C:\Users\Jorge\Desktop\space-xplorer\node_modules\node-sass
node scripts/install.js
Downloading binary from https://github.com/sass/node-sass/releases/download/v4.11.0/win32-x64-72_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.11.0/win32-x64-72_binding.node":
HTTP error 404 Not Found
Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.
export HTTP_PROXY=http://example.com:1234
or configure npm proxy via
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass#4.11.0 postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass#4.11.0 postinstall 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:
npm ERR! C:\Users\Jorge\AppData\Roaming\npm-cache_logs\2020-01-23T22_44_17_513Z-debug.log
This issue is coming because of compatibility issue of node version and node sass version.
You need to downgrade node version to 10 to install node sass 4.1.0. It is not compatible with version 12 of node.
See this discussion for the same issue.
Compatible versions are listed on the readme https://github.com/sass/node-sass#supported-nodejs-versions-vary-by-release-please-consult-the-releases-page-below-is-a-quick-guide-for-minimium-support
Following 2 lines of code will resolve this error
npm run build
npm start
you should ask a question and provide some explanation, not just throw an error up and expect an answer. But I've seen this before:
Basically NPM is trying lacking a dependency for loading node-sass, and its fallback is to get the file it needs from github.
Looks like you're behind a firewall that blocks you from direct access to github, but all you actually need is that file bindings file.
You would have to have a proxy server that is allowed to access github, or download the binary file yourself.
I downgraded the node from 14.8 to 12.18.3, but it did NOT solve the problem.
but after that, as crazy as it is may sound, I deleted the package-lock.json and tried to install the package again and solved the problem.

ng-add & npm link - how to mock npm registry

I am developing a schematics collection for #angular/cli. I would like to test locally how it is working.
Is it possible to test ng-add CLI feature locally?
After linking project with npm link and running ng add myFeature, #angular/cli tries to download the desired library from the npm, what causes following issue:
npm ERR! code E404
npm ERR! 404 Not Found: myLibrary#latest
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/mtreder/.npm/_logs/2018-05-09T10_13_58_291Z-debug.log
Package install failed, see above.
Package install failed, see above.
Can I somehow mock, npm registry to my local environment?
You can use verdaccio to mock a local registry and publish your own stuff and resolve the remaining dependencies from npmjs.
https://www.verdaccio.org/
Here some answer might helpful for you.
Private and Public NPM Package Install in Single Command
I'm not sure whether this 100% answer your question, but, I hope it helps.

Categories