Re-enabling typescript Node test with Node v8 #1190
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Explicitly adding node.js 8 type definitions before ClientResponse interface was removed due to deprecation.
PR checklist
./bin/
to update Petstore sample so that CIs can verify the change. (For instance, only need to run./bin/{LANG}-petstore.sh
and./bin/security/{LANG}-petstore.sh
if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in.\bin\windows\
.master
,3.4.x
,4.0.x
. Default:master
.Description of the PR
As requested in: #1138 trying to fix issue with typescript compiler for typescript-node test.
This seems to be a result of a change in the https://github.com/DefinitelyTyped/DefinitelyTyped repo.
They have deprecated the ClientResponse interface in node 10.
To resolve (at least until the generator uses the new IncomingMessage interface), I've specifically used the type definitions for node 8 in the relevant package.mustache file.
I've ran the sample, installed node_modules and then confirmed that I can run tsc and see the compiled JavaScript.
Regards,
Omer.