Don't automatically include all types from dependencies #3704
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.
This produces an error if you try to use something from a global scope accidentally. It's only needed for "ambient" definitions; if the thing is included directly (like for all of the Node libraries like
fs
) then its types come along with it automatically.Also:
/// <reference />
usage because it does the same thing (see Using /// <reference lib="dom" /> in a .d.ts typescript declaration file has global effects microsoft/TypeScript#33901).@types/node
dependency (TypeScript has that built in).npm run lint
Issue: #3702
Requirements for PR author:
.unimplemented()
./** documented */
and new helper files are found inhelper_index.txt
.Requirements for reviewer sign-off:
When landing this PR, be sure to make any necessary issue status updates.