You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 16, 2021. It is now read-only.
By default, TypeScript discovers ambient types under node_modules/@types/* to be resolvable. For example, a .ts file can just contain import * as fs from 'fs' and it works if the node typings are installed.
Under bazel the types must be explicitly referenced, eg. /// <reference types="node"/>
It doesn't help to list the types in the tsconfig compilerOptions.types[] which is not surprising since IIUC that only restricts which types the compiler includes in resolution.
We noticed this yesterday in the Angular team (cc @matsko and @IgorMinar), independently reported in #30.
The text was updated successfully, but these errors were encountered:
By default, TypeScript discovers ambient types under
node_modules/@types/*
to be resolvable. For example, a .ts file can just containimport * as fs from 'fs'
and it works if the node typings are installed.Under bazel the types must be explicitly referenced, eg.
/// <reference types="node"/>
It doesn't help to list the types in the tsconfig
compilerOptions.types[]
which is not surprising since IIUC that only restricts which types the compiler includes in resolution.We noticed this yesterday in the Angular team (cc @matsko and @IgorMinar), independently reported in #30.
The text was updated successfully, but these errors were encountered: