[Discussion] Better Way to Declare Globals in JavaScript files

Problem Using the new checkJs feature, it is currently difficult to tell TypeScript about a global variable:

// @ts-check

myGlobal

window.myVar = 'foo';

The only way around this that I know is to create a .d.ts file that defines these:

interface Window {
    myVar: string;
}

declare var myGlobal: string;

JavaScript users should not have to write *.d.ts files.

Possible Approaches @egamma proposes that may be able to use the global comment from ESlint http://eslint.org/docs/user-guide/configuring : /* global var1, var2 */

I’d also be interested to see if we could put type information in a jsdoc somehow, something like:

/**
 * @global {string} myGlobal 
 */

[mhegazy]

JavaScript users should not have to write *.d.ts files.

Why is that? Js users are already using dts files from @types; so does not seem totally foreign concept.

[thw0rted]

As a vanilla-JS user who just started using checkJs, it would be really nice if my eslint comment (/* global myVar */) worked with TS so I didn’t have to document my global in two different ways for two different checkers. I hope that the TypeScript team supports the goal of checkJs working on any valid JS without having to add a .d.ts file to your build just to make the checker happy.