Add windowsVerbatimArguments for node child_process

[andrewstucki]

To go along with nodejs/node#16299.

• Use a meaningful title for the pull request. Include the name of the package modified.
• Test the change in your own code. (Compile and run.)
• Follow the advice from the readme.
• Avoid common mistakes.
• Run npm run lint package-name (or tsc if no tslint.json is present).

If changing an existing definition:

• Provide a URL to documentation or source code which provides context for the suggested changes: Add windowsVerbatimArguments docs for child_process.spawn nodejs/node#16299

[dt-bot]

types/node/index.d.ts

to authors (@DefinitelyTyped/DefinitelyTyped @parambirs @tellnes @WilcoBakker @octo-sniffle @smac89 @Flarna @mwiktorczyk @wwwy3y3 @DeividasBakanas @kjin @alvis Microsoft TypeScript (account can't be detected)). Could you review this PR?
👍 or 👎?

[typescript-bot]

@andrewstucki Please fix the failures indicated in the Travis CI log.

[andrewstucki]

Closing because of PR build timeouts

[andrewstucki]

Re-opening to re-run failed test because of PR build timeouts

[andrewstucki]

I don't think that this is going to pass in travis due to the sheer number of type definitions that are affected by the definitions in types/node. The build is timing out while running the tests because it's going through pretty much every single test possible.

[Flarna]

If I understand the node source code correct then exeFile allows also to specify windowsVerbatimArguments.

[andrewstucki]

Looks like @Flarna is right. execFile doesn't override shell, so it should still be valid to pass in windowsVerbatimArguments. Updated.

[andrewstucki]

so... wondering what to do with this given that the build can't possibly pass due to the fact that it requires testing 1211 packages and exceeds Travis's time limit for jobs every time it runs?

[smac89]

@andrewstucki I believe you can do something like:

Forking the repo, create the travis hook on your account, run the tests there and try to do another commit after that. Travis will be able to skip running the long tests if you have already run it through travis once.

[andrewstucki]

@smac89 I enabled travis on my branch and am going to see if it can pass there, but seeing as there appears to be a global travis timeout of 50 mins for jobs and the CI build above was canceled at 49:57, I'm kind of doubtful that I can get the tests to pass there.

[andrewstucki]

See #20308

[RyanCavanaugh]

@andrewstucki Please fix the failures indicated in the Travis CI log.

[andrewstucki]

@RyanCavanaugh as mentioned multiple times, this relates to #20308 -- the build is timing out because of the fact that this is a change to one of the definitions for node which is a dependency of pretty much every other definition in this project. It's not possible to fix because Travis times out before it can finish testing every single type definition.

[andrewstucki]

@andy-ms noticed you resolved and merged #20185

Seeing as this is related because of the Travis timeouts and has sat here untouched for 2 weeks, think you could take a look? Otherwise I think I'm just going to close this PR soon as it looks like it's getting no attention.