Update package.json engines field

[sebmarkbage]

yarn warns about this.

[NTillmann]

We had some issues with a particular node.js version > 7.0.0 --- somehow we managed to trigger a JIT crash! So this needs some testing with all our workloads.

[sebmarkbage]

Interesting. The node environment that I have been building out shims for is 7! So it won't work with 6 atm. :)

[hermanventer]

Can you run "npm run validate" on your system without any issue? If so, can you tell us which version of Node you are using to run it?

[sebmarkbage]

I can confirm that I'm hitting this bug with v7.9.0.

[sebmarkbage]

The only place I can repro it is in tests though. It seems like a bug in contextify (the "vm" module used by the test runner).

var vm = require('vm');
let script = new vm.Script(`
  var global = this; var self = this;
  Object.defineProperty(global, "p", {
    configurable: true,
    enumerable: true,
    get: function () { throw new Error("42"); }
  });
`, { cachedDataProduced: false });
script.runInNewContext({});

If that's the only case I think we should expand the allowed engine range so that people can use the npm package outside of contributing to the project itself (i.e. running tests). While we try to fix the test.

[sebmarkbage]

So what happens is that contextify tries to copy all the properties over and one of them throws which messes up the native side. I think this is covered by the bug nodejs/node#6283

https://github.com/nodejs/node/blob/v7.10.0/src/node_contextify.cc#L96-L117

[sebmarkbage]

I have been getting some additional timeouts in Test262 on this version. Let me know if we'll need to bump any timeout values.

[hermanventer]

I find the timeouts to be non deterministic on my setup. Perhaps not too surprising. The time-out setting for the CI is a bit more generous. I'm OK with leaving things as is as long as CI does not get to be flaky.