Page MenuHomePhabricator

Fix a bad method call signature throwing exceptions in newer Node
ClosedPublic

Authored by epriestley on Dec 10 2018, 7:43 PM.
Tags
None
Referenced Files
F15416050: D19860.id47423.diff
Thu, Mar 20, 8:56 AM
F15406657: D19860.id.diff
Tue, Mar 18, 1:09 PM
F15401929: D19860.diff
Mon, Mar 17, 7:48 PM
F15308969: D19860.id47439.diff
Thu, Mar 6, 6:47 AM
F15308966: D19860.id47423.diff
Thu, Mar 6, 6:47 AM
F15308965: D19860.id.diff
Thu, Mar 6, 6:47 AM
F15308963: D19860.diff
Thu, Mar 6, 6:47 AM
F15287578: D19860.diff
Tue, Mar 4, 7:53 PM
Subscribers
None

Details

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.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable