Yes, it exists (the 'engine' field).
Re:Io.js 2.0.0 Released
by BinaryIdiot on Tuesday May 05, 2015 @03:27AM
(#9491290)
This exists but now you're limiting your audience to use APIs and syntax in a slightly newer, different version of node (io.js). I'm not convinced that's worth it in my opinion. I'm not sure npm can support using the same package name deployed under different engines (it doesn't appear to as far as I can tell) but that's annoying to maintain.
This probably already exists in node world regarding binary dependencies. I use at least one that's only compatible with 0.10 but there's no way to know that until you get a build error on 0.12.