Repository navigation
Object mapping string to boolean or Object gets typed instead to any with new JS->declaration support #34914
Description
C:\T\tsrc>npm ls
C:\T\tsrc
`-- typescript@3.7.1-rc
C:\T\tsrc>type example2.js
"use strict";
/**
* Map of string to boolean or Object.
*
* @typedef {Object.<string, boolean | Object>} MyMap
*/
C:\T\tsrc>node_modules\.bin\tsc --allowjs --declaration --outdir out example2.js
C:\T\tsrc>type out\example2.d.ts
/**
* Map of string to boolean or Object.
*/
type MyMap = {
[x: string]: any;
};
C:\T\tsrc>
Activity
RyanCavanaugh commentedon Nov 8, 2019
Objectis an alias foranyunlessnoImplicitAnyis on. I believe Nathan Shively-Sanders (@sandersn) offered up some other workarounds offline?We should try making
objectbeobjectin JS Doc now that we have a real object primitive typesandersn commentedon Jan 10, 2020
This is something we ask periodically. When I recently removed the
object=anyrewrite when noImplicitAny is on, I found that webpack, in particular, still relies on it, despite checking their code with typescript. I expect the results would be similar forObject=any.