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
F15589309: D19860.id47423.diff
Fri, May 9, 12:57 PM
F15566833: D19860.id.diff
Thu, May 1, 11:58 PM
F15534579: D19860.id47439.diff
Thu, Apr 24, 12:53 AM
F15515588: D19860.id.diff
Fri, Apr 18, 11:40 AM
F15513317: D19860.diff
Thu, Apr 17, 5:59 PM
F15479054: D19860.diff
Apr 8 2025, 5:04 AM
F15457486: D19860.diff
Mar 30 2025, 5:10 PM
F15416050: D19860.id47423.diff
Mar 20 2025, 8:56 AM
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