Anyone using a pre-release or nightly build of node or iojs is used to seeing a stream of warning about unmet engine requirements. Annoying, but acceptable.

The problem comes when one of those packages uses "engineStrict": true.

$ semver -r ">= 0.10" v0.10.35 v0.11.14 v0.11.15-pre v1.0.1 v1.0.2 v1.0.3-nightly2015011850177fb13c
0.10.35
0.11.14
1.0.1
1.0.2

I have no idea how this could/would be fixed in npm without abandoning semver for that field, but the problem is real and this seems like the best place to draw attention to it. If nothing else it can be an issue to cite when reporting issues and submitting PRs to the modules making use of "node": ">= 0.10" and expecting it to allow "anything 0.10 or newer".