When I try to install NestJS via
npm i -g #nestjs/cli, I get:
npm WARN deprecated sourcemap-codec#1.4.8: Please use #jridgewell/sourcemap-codec instead
Is this expected behavior to install Nest? Or is something wrong here?
Related
While trying to create a new project with angular, I used the command ng new my-dream-app in command prompt and I receiver the following error message:
Installing packages...npm WARN deprecated tslint#6.1.1: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated fsevents#1.2.12: fsevents 1 will break on node v14+. Upgrade to fsevents 2 with massive improvements.
npm ERR! Unexpected end of JSON input while parsing near '...t-config-prettier":"^'
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Izormen Onotieose\AppData\Roaming\npm-cache\_logs\2020-04-21T14_21_50_827Z-debug.log
× Package install failed, see above.
Pls how do I go about this?
It looks like it is a cache error. Try this:
npm cache clean --force
npm install -g #angular/cli
Cheers!
Try cleaning the cache and reinstalling global Angular CLI.
Open CMD as administrator and run
npm cache clean --force
npm install -g #angular/cli
I'm currently learning angular 9 so when i tried to install node js and npm with latest version that is node version 12.* and npm version 6.14.*. I'm facing problem whith ng new and npm install command
Issues are as follows:
sudo npm install
npm WARN deprecated mkdirp#0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm ERR! Unexpected end of JSON input while parsing near '...ure":"-----BEGIN PGP '
npm ERR! A complete log of this run can be found in:
npm ERR! /home/frustrated_coder/.npm/_logs/2020-03-29T14_31_40_275Z-debug.log
ng new angular-test
Installing packages...npm WARN deprecated mkdirp#0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm ERR! Unexpected end of JSON input while parsing near '...200772","tarball":"ht'
npm ERR! A complete log of this run can be found in:
npm ERR! /home/frustrated_coder/.npm/_logs/2020-03-29T14_20_56_952Z-debug.log
✖ Package install failed, see above.
The Schematic workflow failed. See above.
Also i working on angular-electron but the majority of the problem is with that as well due to npm install command in it.
This is the https://github.com/maximegris/angular-electron url from where i'm cloning angular electron.
Use Windows Powershell as an administrator and run;
npm cache clean --force
npm install -g #angular/cli
I am new to node-red interface, and I am trying to set up a distributed flow using DNR editor created by JS Foundation. While attempting to install via both npm and git clone I have encountered many errors that prevented installation. Could someone please help me take a look at the problem and see what I have done wrong? I have copied the shell log to a text file with some images attached. Thanks in advance for your time and attention!
I tried to reinstall one "deprecated" package (bcrypt#3.0.) but the npm deprecate message still persist.
C:\Users\WILL>npm install -g dnr-editor
npm WARN deprecated bcrypt#1.0.3: bcrypt < v2.0.0 is susceptible to bcrypt wrap-around bug. Upgrade to bcrypt >= v2.0.0 for improved support for newer bcrypt hashes
npm WARN deprecated mongodb#2.1.21: Please upgrade to 2.2.19 or higher
npm WARN deprecated node-uuid#1.4.8: Use uuid module instead
npm WARN deprecated mailparser#0.6.2: Mailparser versions older than v2.3.0 are deprecated
npm WARN deprecated nodemailer#1.11.0: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated mimelib#0.3.1: This project is unmaintained
npm WARN deprecated mailcomposer#2.1.0: This project is unmaintained
npm WARN deprecated buildmail#2.0.0: This project is unmaintained
C:\Users\WILL\AppData\Roaming\npm\dnr-editor -> C:\Users\WILL\AppData\Roaming\npm\node_modules\dnr-editor\red.js
npm uninstall --save bcrypt
&&
npm install --save bcryptjs
I am trying to do 'npm install' inside one of my folders but i am getting error code E403 Forbidden :
npm WARN deprecated node-uuid#1.4.8: Use uuid module instead
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher
to avoid a RegExp DoS issue
npm WARN deprecated minimatch#0.2.14: Please update to minimatch 3.0.2 or higher
to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs#1.2.3: graceful-fs v3.0.0 and before will fail
on node releases >= v7.0. Please update to graceful-fs#^4.0.0 as soon as
possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.0.0
(node_modules\chokidar\node_modules\fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: 403 Forbidden:
https://registry.npmjs.org/fsevents/-/fsevents-1.1.3.tgz
npm ERR! code E403
npm ERR! 403 Forbidden: binary-extensions#^1.0.0
My npm version is 5.5.1
My node version is v8.9.1
Also my system was formatted today and I had to re-install and re-setup everything from scratch. npm install was working till yesterday before my system was formatted.
I have attached the log file here.
https://github.com/angular/angular-cli/files/1499291/2017-11-23T13_25_27_656Z-debug.log
Thanks in advance
EDIT: every npm install is failing.
for reference here are the entries in my .npmrc file:
registry=http://registry.npmjs.org/
proxy=http://user_name:password#proxy:port
https-proxy=http://user_name:password#proxy:port
strict-ssl=false
I have tried many commands to get this working but no luck.
Note: my password contains '#' symbol but i have encoded it in my .npmrc file as %40
Ok, so i got around this particular problem. Seems like i had to update http to https in registry, and E403 was gone. But still i was facing other issues so decided to downgrade npm to 3.10.10 and node to 6.10.3.
From the first line it's saying old node-uuid module is deprecated and won't be maintained moving forward. Try reinstalling using these commands.
npm uninstall --save node-uuid
npm install --save uuid
In the second line it's asking for installation of minimatch
So try running the command :
npm install -g minimatch#3.0.4
I am using nvm for managing node versions. I have installed it as a plugin to zsh via zsh-nvm. I have installed two versions of node - v6.1.0 and v.0.10.42. Since I am working on a project, which uses the latter one, I have set it at the default one. Now, every time I open a terminal window, I get these warnings:
npm WARN deprecated This version of npm lacks support for important features,
npm WARN deprecated such as scoped packages, offered by the primary npm
npm WARN deprecated registry. Consider upgrading to at least npm#2, if not the
npm WARN deprecated latest stable version. To upgrade to npm#2, run:
npm WARN deprecated
npm WARN deprecated npm -g install npm#latest-2
npm WARN deprecated
npm WARN deprecated To upgrade to the latest stable version, run:
npm WARN deprecated
npm WARN deprecated npm -g install npm#latest
npm WARN deprecated
npm WARN deprecated (Depending on how Node.js was installed on your system, you
npm WARN deprecated may need to prefix the preceding commands with `sudo`, or if
npm WARN deprecated on Windows, run them from an Administrator prompt.)
npm WARN deprecated
npm WARN deprecated If you're running the version of npm bundled with
npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS
npm WARN deprecated will be bundled with a version of npm#2, which has some small
npm WARN deprecated backwards-incompatible changes made to `npm run-script` and
npm WARN deprecated semver behavior.
I tried adding a ~/.npmrc file, in which I put loglevel="error", but I still get these warnings. I guess I need to put some setting in my .zshrc file. Could you point me to which one?
As far as I'm aware, the only way to suppress these warnings (from npm) is to use a version of npm that doesn't emit them.
NODE_NO_WARNINGS=1 npm install ...