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.
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 https://github.com/microsoft/TypeScript/issues/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.