alpha.9 is not properly set up in npm

[mLaird]

Bug, feature request, or proposal:

When I put "@angular2-material": "^2.0.0-alpha.9", in my project's package.json and do an npm outdated depth=0, I get a lengthy npm error report. This happens whether or not the old alpha.8-2 entries are in package.json i.e., in both cases. The error report is:

$ npm outdated --depth=0
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" "outdated" "--depth=0"
npm ERR! node v5.0.0
npm ERR! npm v3.3.6
npm ERR! code EMISSINGARG

npm ERR! typeerror Error: Missing required argument #2
npm ERR! typeerror at exports.findRequirement (C:\Program Files\nodejs\node_ modules\npm\lib\install\deps.js:475:3)
npm ERR! typeerror at C:\Program Files\nodejs\node_modules\npm\lib\install\d eps.js:90:19
npm ERR! typeerror at zalgoSafe (C:\Program Files\nodejs\node_modules\npm\no de_modules\dezalgo\dezalgo.js:20:10)
npm ERR! typeerror at finalize (C:\Program Files\nodejs\node_modules\npm\nod e_modules\realize-package-specifier\index.js:37:5)
npm ERR! typeerror at C:\Program Files\nodejs\node_modules\npm\node_modules\ realize-package-specifier\index.js:22:20
npm ERR! typeerror at FSReqWrap.oncomplete (fs.js:82:15)
npm ERR! typeerror This is an error with npm itself. Please report this error at :
npm ERR! typeerror http://github.com/npm/npm/issues

What is the expected behavior?

I should get a standard outdated report showing alpha.9 as MISSING and alpha.9 as Latest available.

What is the current behavior?

I get the above error statement, not the standard npm outdated report.

[PascalTemel]

use @angular/material instead.

[mLaird]

I tried @angular/material, and get the same error - (see below). I also
have to say this new name is a mistake by the MD team because it creates
confusion about which Angular it matches. Here is the continuing error
report.

$ npm outdated --depth=0
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" "outdated" "--depth=0"
npm ERR! node v5.0.0
npm ERR! npm v3.3.6
npm ERR! code EMISSINGARG

npm ERR! typeerror Error: Missing required argument #2
npm ERR! typeerror at exports.findRequirement (C:\Program
Files\nodejs\node_modules\npm\lib\install\deps.js:475:3)
npm ERR! typeerror at C:\Program
Files\nodejs\node_modules\npm\lib\install\deps.js:90:19
npm ERR! typeerror at zalgoSafe (C:\Program
Files\nodejs\node_modules\npm\node_modules\dezalgo\dezalgo.js:20:10)
npm ERR! typeerror at finalize (C:\Program
Files\nodejs\node_modules\npm\node_modules\realize-package-specifier\index.js:37:5)
npm ERR! typeerror at C:\Program
Files\nodejs\node_modules\npm\node_modules\realize-package-specifier\index.js:22:20
npm ERR! typeerror at FSReqWrap.oncomplete (fs.js:82:15)
npm ERR! typeerror This is an error with npm itself. Please report this
error at:
npm ERR! typeerror http://github.com/npm/npm/issues

On Thu, Oct 6, 2016 at 2:43 AM, Pascal Temel notifications@github.com
wrote:

use @angular/material instead.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1435 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADDSb58nIzi13ARRCWzJVX8tx0votrUbks5qxJh3gaJpZM4KPMjz
.

Mike Laird

12 Arbor Creek Drive, Pittsford, New York 14534
mlaird@alum.mit.edu

". . . remembering on both sides that civility is not a sign of weakness,
and sincerity is always subject to proof. Let us never negotiate out of
fear, but let us never fear to negotiate." - John F. Kennedy

[jelbourn]

There is no alpha.9 version for the old angular2-material packages. All new updates are on @angular/material. Latest version is 2.0.0-alpha.9-3.

https://www.npmjs.com/package/@angular/material

I'd suggest wiping out your node_module and reinstalling, possibly with a node version other than 5.*, which isn't supported any longer. As far as I can tell, this isn't a problem with material and is more likely an environment issue.

[mLaird]

@jeremy Elbourn, Thanks. You guessed well. I had Node 5.0, and when I
re-installed to Node 4.6, everything worked.

If you are part of the Angular2 Material team, note that neither the npm
page nor the Getting Started page say anything about Node 5.0 not being
supported. FWIW, I find it odd to install angular/material and get a
folder named @angular-material. But/overall, @thanks-I'm OK.

;-)

On Fri, Oct 7, 2016 at 3:32 PM, Jeremy Elbourn notifications@github.com
wrote:

There is no alpha.9 version for the old angular2-material packages. All
new updates are on @angular/material. Latest version is 2.0.0-alpha.9-3.

https://www.npmjs.com/package/@angular/material

I'd suggest wiping out your node_module and reinstalling, possibly with a
node version other than 5.*, which isn't supported any longer. As far as I
can tell, this isn't a problem with material and is more likely an
environment issue.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1435 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADDSb4Qb948bEGqdsPjIKiSn-uPBlwxLks5qxp5jgaJpZM4KPMjz
.

Mike Laird

12 Arbor Creek Drive, Pittsford, New York 14534
mlaird@alum.mit.edu

". . . remembering on both sides that civility is not a sign of weakness,
and sincerity is always subject to proof. Let us never negotiate out of
fear, but let us never fear to negotiate." - John F. Kennedy

[angular-automatic-lock-bot]

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.}