"engines" seems to be ignored

[naholyr]

Scenario:

• just published copycast@5.0.1 (tagged "next") which targets node ≥ 6.0.0
• when I run npm i -g copycast@next (from another directory, to be sure it's not related to my cwd) using node 5.10.1 / npm 3.8.3, install works fine, no warning
• I expected a failure :(

package.json:

…
  engineStrict: true,
  engines: { node: '>= 6.0.0' },
…

Note: I'm aware that "engines" is ignored when you npm install your module from its working directory, this is not the situation described here.

[MiLk]

It seems to be broken since npm v3.6.0.

[naholyr]

Thanks for the test, I may have messed up during mines because at some point installs even with npm@2 it was ignored, but I used "engine", "engines", different syntaxes, tried anything :D

As it's a simple warning anyway, I'll go with a preinstall script I guess.

[iarna]

The warnings should show up after your install completes now, after the summary install tree.

[iarna]

(The goal being to highlight the warnings better when you have a full screen summary tree.)

[MiLk]

Nothing is showing up.

npm v3.6.0

npm v3.8.8

[naholyr]

Nope I never had any warning, before or after summary tree. Today I
replaced the mention by a preinstall script doing the job as intended
(triggered before useless downloads and blocking installation as it won't
work anyway).

On Tue, May 3, 2016 at 3:41 AM Emilien Kenler notifications@github.com
wrote:

Nothing is showing up.

npm v3.6.0
[image: 2016-05-03-103649_415x674_scrot]
https://cloud.githubusercontent.com/assets/29782/14972800/03417a00-111b-11e6-849b-5cf081941f9f.png
[image: 2016-05-03-103613_874x988_scrot]
https://cloud.githubusercontent.com/assets/29782/14972801/0343c616-111b-11e6-9b96-51f0c360bf53.png

npm v3.8.8
[image: 2016-05-03-104001_384x300_scrot]
https://cloud.githubusercontent.com/assets/29782/14972833/70060426-111b-11e6-891f-66e04e248d48.png
[image: 2016-05-03-104011_799x309_scrot]
https://cloud.githubusercontent.com/assets/29782/14972832/6fe52602-111b-11e6-9f78-d5483bd2f670.png

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#12486 (comment)

[jdalton]

Seeing this issue in npm -v 2.15.1. When installing dev deps locally npm i I don't get a warning.

[nicolasnoble]

I'm fairly impressed that this issue doesn't have any more traction that this. One documented feature of npm hasn't been working for more than two years now.