Angular-cli: Deprecated

Created on 20 Mar 2018  Â·  20Comments  Â·  Source: angular/angular-cli

Versions

ng v 1.7.3
node v 8.10.0
npm -v 5.6.0
<!--
Output from: `ng --version`.  
If nothing, output from: `node --version` and `npm --version`.
  Windows (7/8/10). Linux (incl. distribution). macOS (El Capitan? Sierra?)
-->

Repro steps

  • ng new test1

Observed behavior

<!-- Normally this includes a stack trace and some more information. -->


I have the next behavior when i install a new angular project.

npm WARN deprecated [email protected]: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated [email protected]: This project is unmaintained
npm WARN deprecated [email protected]: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: This project is unmaintained
npm WARN deprecated [email protected]: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EINTEGRITY: sha1-FERbahYTz04F3WHDwyVtDpXAQh4= integrity checksum failed when using sha1: wanted sha1-FERbahYTz04F3WHDwyVtDpXAQh4= but got sha512-clg9raJTY0EOo5pVZKX3ZlMjlYzVU73L71q5OV1jhE2Uezb7oF94jh4CvwrW6wInquQAdhOxJz5VDF2TLUGmmA==. (7483 bytes)
npm WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.

Desired behavior

Install normally

Mention any other details that might be useful (optional)

It run normally when i use ng serve, but i have issues when install some libraries and it done show the page. It show a white page and none error.

picture jhfaber
👍12

Most helpful comment

hello guys,

I had the same issue.

But I solved it by doing npm install i -g npm-check-updates
And after in the project folder doing ncu -u

Hope this can help. =)

picture rfmsimoes on 29 Mar 2018
👍7

All 20 comments

Can you please provide some additional information?
What packages did you include? How did you include them?
Does your page actually show noe error at all, not even in the browser console? (Chrome Devtools)
Thanks!

fmalcher picture fmalcher on 20 Mar 2018

I noticed the same npm deprecated warning, when I ran 'ng new frontend'.

```

ng new frontend
create frontend/README.md (1024 bytes)
create frontend/.angular-cli.json (1243 bytes)
create frontend/.editorconfig (245 bytes)
create frontend/.gitignore (544 bytes)
create frontend/src/assets/.gitkeep (0 bytes)
create frontend/src/environments/environment.prod.ts (51 bytes)
create frontend/src/environments/environment.ts (387 bytes)
create frontend/src/favicon.ico (5430 bytes)
create frontend/src/index.html (295 bytes)
create frontend/src/main.ts (370 bytes)
create frontend/src/polyfills.ts (3114 bytes)
create frontend/src/styles.css (80 bytes)
create frontend/src/test.ts (642 bytes)
create frontend/src/tsconfig.app.json (211 bytes)
create frontend/src/tsconfig.spec.json (283 bytes)
create frontend/src/typings.d.ts (104 bytes)
create frontend/e2e/app.e2e-spec.ts (290 bytes)
create frontend/e2e/app.po.ts (208 bytes)
create frontend/e2e/tsconfig.e2e.json (235 bytes)
create frontend/karma.conf.js (923 bytes)
create frontend/package.json (1293 bytes)
create frontend/protractor.conf.js (722 bytes)
create frontend/tsconfig.json (363 bytes)
create frontend/tslint.json (3012 bytes)
create frontend/src/app/app.module.ts (316 bytes)
create frontend/src/app/app.component.css (0 bytes)
create frontend/src/app/app.component.html (1141 bytes)
create frontend/src/app/app.component.spec.ts (986 bytes)
create frontend/src/app/app.component.ts (207 bytes)
npm WARN deprecated [email protected]: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated [email protected]: Use uuid module instead

ng version

_                      _                 ____ _     ___

/ _ __ __ _ _ _| | __ _ _ __ / ___| | |_ _|
/ â–³ | '_ / _| | | | |/ _ | '__| | | | | | |
/ ___ | | | | (_| | |_| | | (_| | | | |___| |___ | |
/_/ __| |_|__, |__,_|_|__,_|_| ____|_____|___|
|___/

Angular CLI: 1.7.3
Node: 8.9.4
OS: darwin x64
Angular:
...

```

mcbeelen picture mcbeelen on 21 Mar 2018

same here from Windows.

Just did an uninstall / cache verify / install of @angular/cli to make sure it wasn't me.

$ ng v
_                      _                 ____ _     ___
/ \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
/ â–³ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
/ ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
/_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
|___/

Angular CLI: 1.7.3
Node: 6.10.3
OS: win32 x64
Angular:
...

jc_ry@JRYAN-PC MINGW64 /c/dev
$ ng new modules-ex100
  create modules-ex100/e2e/app.e2e-spec.ts (295 bytes)
  create modules-ex100/e2e/app.po.ts (208 bytes)
  create modules-ex100/e2e/tsconfig.e2e.json (235 bytes)
  create modules-ex100/karma.conf.js (923 bytes)
  create modules-ex100/package.json (1298 bytes)
  create modules-ex100/protractor.conf.js (722 bytes)
  create modules-ex100/README.md (1028 bytes)
  create modules-ex100/tsconfig.json (363 bytes)
  create modules-ex100/tslint.json (3012 bytes)
  create modules-ex100/.angular-cli.json (1248 bytes)
  create modules-ex100/.editorconfig (245 bytes)
  create modules-ex100/.gitignore (544 bytes)
  create modules-ex100/src/assets/.gitkeep (0 bytes)
  create modules-ex100/src/environments/environment.prod.ts (51 bytes)
  create modules-ex100/src/environments/environment.ts (387 bytes)
  create modules-ex100/src/favicon.ico (5430 bytes)
  create modules-ex100/src/index.html (299 bytes)
  create modules-ex100/src/main.ts (370 bytes)
  create modules-ex100/src/polyfills.ts (3114 bytes)
  create modules-ex100/src/styles.css (80 bytes)
  create modules-ex100/src/test.ts (642 bytes)
  create modules-ex100/src/tsconfig.app.json (211 bytes)
  create modules-ex100/src/tsconfig.spec.json (283 bytes)
  create modules-ex100/src/typings.d.ts (104 bytes)
  create modules-ex100/src/app/app.module.ts (316 bytes)
  create modules-ex100/src/app/app.component.html (1141 bytes)
  create modules-ex100/src/app/app.component.spec.ts (986 bytes)
  create modules-ex100/src/app/app.component.ts (207 bytes)
  create modules-ex100/src/app/app.component.css (0 bytes)
npm WARN deprecated [email protected]: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated [email protected]: This project is unmaintained
npm WARN deprecated [email protected]: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: This project is unmaintained
npm WARN deprecated [email protected]: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0

> [email protected] install C:\dev\modules-ex100\node_modules\uws
> node-gyp rebuild > build_log.txt 2>&1 || exit 0


> [email protected] install C:\dev\modules-ex100\node_modules\node-sass
> node scripts/install.js

Cached binary found at C:\Users\jc_ry\AppData\Roaming\npm-cache\node-sass\4.7.2\win32-x64-48_binding.node

> [email protected] postinstall C:\dev\modules-ex100\node_modules\webpack\node_modules\uglifyjs-webpack-plugin
> node lib/post_install.js


> [email protected] postinstall C:\dev\modules-ex100\node_modules\node-sass
> node scripts/build.js

Binary found at C:\Dev\modules-ex100\node_modules\node-sass\vendor\win32-x64-48\binding.node
Testing binary
Binary is fine
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

added 1264 packages from 1239 contributors in 49.06s
Project 'modules-ex100' successfully created.
unff picture unff on 23 Mar 2018

same issue with vue-cli . So it is not only for angular-cli.
npm WARN deprecated [email protected]: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0

pam81 picture pam81 on 24 Mar 2018

Same here, its just a bunch of warnings anyway would be great it does behave the way it should.

Windows 10 x64 1709
Angular CLI: 1.7.3
Node: 9.9.0

My log:

> ng new Angular-app
  create Angular-app/e2e/app.e2e-spec.ts (293 bytes)
  create Angular-app/e2e/app.po.ts (208 bytes)
  create Angular-app/e2e/tsconfig.e2e.json (235 bytes)
  create Angular-app/karma.conf.js (923 bytes)
  create Angular-app/package.json (1296 bytes)
  create Angular-app/protractor.conf.js (722 bytes)
  create Angular-app/README.md (1026 bytes)
  create Angular-app/tsconfig.json (363 bytes)
  create Angular-app/tslint.json (3012 bytes)
  create Angular-app/.angular-cli.json (1246 bytes)
  create Angular-app/.editorconfig (245 bytes)
  create Angular-app/.gitignore (544 bytes)
  create Angular-app/src/assets/.gitkeep (0 bytes)
  create Angular-app/src/environments/environment.prod.ts (51 bytes)
  create Angular-app/src/environments/environment.ts (387 bytes)
  create Angular-app/src/favicon.ico (5430 bytes)
  create Angular-app/src/index.html (297 bytes)
  create Angular-app/src/main.ts (370 bytes)
  create Angular-app/src/polyfills.ts (3114 bytes)
  create Angular-app/src/styles.css (80 bytes)
  create Angular-app/src/test.ts (642 bytes)
  create Angular-app/src/tsconfig.app.json (211 bytes)
  create Angular-app/src/tsconfig.spec.json (283 bytes)
  create Angular-app/src/typings.d.ts (104 bytes)
  create Angular-app/src/app/app.module.ts (316 bytes)
  create Angular-app/src/app/app.component.html (1141 bytes)
  create Angular-app/src/app/app.component.spec.ts (986 bytes)
  create Angular-app/src/app/app.component.ts (207 bytes)
  create Angular-app/src/app/app.component.css (0 bytes)
npm WARN deprecated [email protected]: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated [email protected]: This project is unmaintained
npm WARN deprecated [email protected]: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: This project is unmaintained
npm WARN deprecated [email protected]: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0

> [email protected] install D:\Workspace\sandbox\Angular\Angular-app\node_modules\uws
> node-gyp rebuild > build_log.txt 2>&1 || exit 0


> [email protected] install D:\Workspace\sandbox\Angular\Angular-app\node_modules\node-sass
> node scripts/install.js

Cached binary found at C:\Users\luciano\AppData\Roaming\npm-cache\node-sass\4.8.3\win32-x64-59_binding.node

> [email protected] postinstall D:\Workspace\sandbox\Angular\Angular-app\node_modules\webpack\node_modules\uglifyjs-webpack-plugin
> node lib/post_install.js


> [email protected] postinstall D:\Workspace\sandbox\Angular\Angular-app\node_modules\node-sass
> node scripts/build.js

Binary found at D:\Workspace\sandbox\Angular\Angular-app\node_modules\node-sass\vendor\win32-x64-59\binding.node
Testing binary
Binary is fine
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

added 1264 packages in 58.408s
Project 'Angular-app' successfully created.
commendatore picture commendatore on 25 Mar 2018

for me these warnings went away after I repeated npm install.

volei picture volei on 28 Mar 2018

I'm an Angular noob, but I almost immediately hit the same behaviour as OP.
Found my problem though. Nothing to do with the "ng new" warnings.

I made the noob mistake of listing "MatListItem" in app.module.ts: @NgModule: imports

Making that one mistake causes the page to render blank, with no warnings or error anywhere I have found...

Should I report this as a separate issue?

peternann picture peternann on 29 Mar 2018

hello guys,

I had the same issue.

But I solved it by doing npm install i -g npm-check-updates
And after in the project folder doing ncu -u

Hope this can help. =)

rfmsimoes picture rfmsimoes on 29 Mar 2018
👍7

@rfmsimoes if you modify and upgrade the dependencies in the packages.json generated by the angular cli, this will result in strange behaviours or errors in your app debugging and compiling , i wouldnt recommend it.

commendatore picture commendatore on 30 Mar 2018

@commendatore you are right.
Although it is a little odd when you generate a new application and get some warnings about outdated files.
Because old version can have exploits and bugs already known but only fixed in the latest version.

But as I said, you are correct when you say it can generate some aditional issues.

rfmsimoes picture rfmsimoes on 30 Mar 2018

me to... tried to install again but get than this one: node_modules appears empty, you may need to run npm install

djamir909 picture djamir909 on 2 Apr 2018

Hello, I have the same "Deprecated" warnings when ng builds new project. My setup:
Angular CLI: 1.7.3 (fresh installation)
Node: 8.10.0 (fresh installation, npm updated to 5.8.0)
OS: linux x64 (more precisely ubuntu 16.04)

totome picture totome on 3 Apr 2018

I'm also getting this error. Any updates as to what is happening?

MarittyaKeu picture MarittyaKeu on 3 Apr 2018

I have a Node v8.11.1 with no additional npm packages (fresh install) in Windows 10 and I also am getting these warnings about the deprecated packages. I upgraded the npm to the latest version by npm install npm@latest -g but it didn't give any help.

mlauronen picture mlauronen on 10 Apr 2018

I tried to intall the angular-cli and there are no issues in the installiation. 

$ npm install -g @angular/cli
/home/sam/.nvm/versions/node/v8.11.1/bin/ng -> /home/sam/.nvm/versions/node/v8.11.1/lib/node_modules/@angular/cli/bin/ng

> [email protected] install /home/sam/.nvm/versions/node/v8.11.1/lib/node_modules/@angular/cli/node_modules/node-sass
> node scripts/install.js

Cached binary found at /home/sam/.npm/node-sass/4.8.3/linux-x64-57_binding.node

> [email protected] postinstall /home/sam/.nvm/versions/node/v8.11.1/lib/node_modules/@angular/cli/node_modules/webpack/node_modules/uglifyjs-webpack-plugin
> node lib/post_install.js


> [email protected] postinstall /home/sam/.nvm/versions/node/v8.11.1/lib/node_modules/@angular/cli/node_modules/node-sass
> node scripts/build.js

Binary found at /home/sam/.nvm/versions/node/v8.11.1/lib/node_modules/@angular/cli/node_modules/node-sass/vendor/linux-x64-57/binding.node
Testing binary
Binary is fine
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/@angular/cli/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

+ @angular/[email protected]
added 925 packages in 143.238s

But when I try to create a new project, I am getting deprecated warning for multiple packages. Here is my log.

  $ ng new my-ap
  create my-ap/README.md (1020 bytes)
  create my-ap/.angular-cli.json (1240 bytes)
  create my-ap/.editorconfig (245 bytes)
  create my-ap/.gitignore (544 bytes)
  create my-ap/src/assets/.gitkeep (0 bytes)
  create my-ap/src/environments/environment.prod.ts (51 bytes)
  create my-ap/src/environments/environment.ts (387 bytes)
  create my-ap/src/favicon.ico (5430 bytes)
  create my-ap/src/index.html (291 bytes)
  create my-ap/src/main.ts (370 bytes)
  create my-ap/src/polyfills.ts (3114 bytes)
  create my-ap/src/styles.css (80 bytes)
  create my-ap/src/test.ts (642 bytes)
  create my-ap/src/tsconfig.app.json (211 bytes)
  create my-ap/src/tsconfig.spec.json (283 bytes)
  create my-ap/src/typings.d.ts (104 bytes)
  create my-ap/e2e/app.e2e-spec.ts (287 bytes)
  create my-ap/e2e/app.po.ts (208 bytes)
  create my-ap/e2e/tsconfig.e2e.json (235 bytes)
  create my-ap/karma.conf.js (923 bytes)
  create my-ap/package.json (1290 bytes)
  create my-ap/protractor.conf.js (722 bytes)
  create my-ap/tsconfig.json (363 bytes)
  create my-ap/tslint.json (3012 bytes)
  create my-ap/src/app/app.module.ts (316 bytes)
  create my-ap/src/app/app.component.css (0 bytes)
  create my-ap/src/app/app.component.html (1141 bytes)
  create my-ap/src/app/app.component.spec.ts (986 bytes)
  create my-ap/src/app/app.component.ts (207 bytes)
npm WARN deprecated [email protected]: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated [email protected]: This project is unmaintained
npm WARN deprecated [email protected]: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: This project is unmaintained
npm WARN deprecated [email protected]: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0

> [email protected] install /home/sam/projects/angular/my-ap/node_modules/uws
> node-gyp rebuild > build_log.txt 2>&1 || exit 0


> [email protected] install /home/sam/projects/angular/my-ap/node_modules/node-sass
> node scripts/install.js

Cached binary found at /home/sam/.npm/node-sass/4.8.3/linux-x64-57_binding.node

> [email protected] postinstall /home/sam/projects/angular/my-ap/node_modules/webpack/node_modules/uglifyjs-webpack-plugin
> node lib/post_install.js


> [email protected] postinstall /home/sam/projects/angular/my-ap/node_modules/node-sass
> node scripts/build.js

Binary found at /home/sam/projects/angular/my-ap/node_modules/node-sass/vendor/linux-x64-57/binding.node
Testing binary
Binary is fine
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 1259 packages in 117.674s
Project 'my-ap' successfully created.

$ ng -v

    _                      _                 ____ _     ___
   / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
  / â–³ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
 / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
/_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
               |___/

Angular CLI: 1.7.4
Node: 8.11.1
OS: linux x64
Angular: 
...
sriramgk picture sriramgk on 17 Apr 2018

Same issue. How can I avoided?

lakinduakash picture lakinduakash on 19 Apr 2018

The magic works for me :

  • Add package-lock.json file into repository. (Or remove it from .gitignore)
  • Remove repo and clone again
  • Install npm packages without warnings
roman-rr picture roman-rr on 21 Apr 2018

@roman-rr What you are saying is a workaround. The deprecated warning should not come without any workaround when we create a new project. I am not sure, I assume the packages are deprecated and the team should review the version of those packages.

sriramgk picture sriramgk on 8 May 2018

This is no longer an issue with CLI V6.0 (karma was downgraded to 1.7.x).

Note the warnings were actually a result of log4js-node which is a dependency of karma v2. related issue: https://github.com/log4js-node/log4js-node/issues/686

clydin picture clydin on 8 May 2018

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_This action has been performed automatically by a bot._

angular-automatic-lock-bot[bot] picture angular-automatic-lock-bot[bot] on 8 Sep 2019
Was this page helpful?
0 / 5 - 0 ratings

Related issues

5amfung picture 5amfung  Â·  3Comments
rwillmer picture rwillmer  Â·  3Comments
delasteve picture delasteve  Â·  3Comments
ericel picture ericel  Â·  3Comments
sysmat picture sysmat  Â·  3Comments