Repository navigation
Triple-slash reference affects all files instead of just the one file that contains it. #19978
Description
Activity
We're having the same problem with Jest, which declares even more ambient definitions than mocha: If one unit test does
/// <reference types="mocha" />, then all the product code can suddenly access these definitions./// <reference types="mocha" />is a global directive. it is an alias to--typesin your tsconfig.json or on the commandline.What
mochadoes is it adds declarations to the global scope, and there is no way to tease out what a global means in one module and not the other..My recommendation here is to have your tests in a separate compilation, and they would include
mocha.My recommendation here is to have your tests in a separate compilation, and they would include
mocha.If we want VS Code IntelliSense for the unit tests, does that mean we need to create a separate package.json and/or tsconfig.json file?
tsconfig.jsonis all you needAutomatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.
- locked and limited conversation to collaborators
on Jun 14, 2018
TypeScript Version: 2.4.2
Code
/// <reference types="mocha" />Expected behavior:
Types from mocha are only available to the test ts file that include this triple-slash reference.
Actual behavior:
Types from mocha are available to all the ts files in the project, including both prod code and test code.
This is unexpected. How do we prevent Mocha test types from accidentally getting into prod code?