Removes reference to node typings and stubs dom interfaces #1228
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.
@blakeembry
I'm only posting a few of the updated service models here since they are updated so frequently.
I removed all instances of
///<reference types="node" />
I tried to include a
tsconfig.json
with the SDK that specifieddom
incompilerOptions.lib
, but I still got XMLHttpRequest (and related) errors in my test app if I excludeddom
.It looks like the route some libraries have taken is to create empty interfaces. Then, if the user includes
dom
the interfaces are merged. I've done this, however this also reduces the effectiveness of type-checking. Short of creating separate definitions for the browser (difficult since this is a combined project), I'm not sure there's a better way to do this.Anyway, would love to get some feedback if you have time.
Note: The first commit has most of the changes (I reverted the streams one for now), I uploaded all the updated definitions in case anyone wanted to test against their existing projects.