epriestley 55a1ef339f Fix a bad method call signature throwing exceptions in newer Node ... Summary: Ref T13222. See PHI996. Ref T10743. For context, perhaps see T12171. Node changed some signatures, behaviors, and error handling here in recent versions. As far as I can tell: - The `script.runInNewContext(...)` method has never taken a `path` parameter, and passing the path has always been wrong. - The `script.runInNewContext(...)` method started taking an `[options]` parameter at some point, and validating it, so the bad `path` parameter now throws. - `vm.createScript(...)` is "soft deprecated" but basically fine, and keeping it looks more compatible. This seems like the smallest and most compatible correct change. Test Plan: Under Node 10, started Aphlict. Before: fatal error on bad `options` parameter to `runInNewContext()` (expected dictionary). After: notification server starts. Reviewers: amckinley Reviewed By: amckinley Maniphest Tasks: T13222, T10743 Differential Revision: https://secure.phabricator.com/D19860		2018-12-10 16:01:00 -08:00
..
d3	Swap charts from gRaphael to D3	2016-02-01 10:36:59 -08:00
font	Remove "Aleo" as specialized font for headers	2017-03-22 09:57:00 -07:00
javelin	Fix a bad method call signature throwing exceptions in newer Node	2018-12-10 16:01:00 -08:00