-
Notifications
You must be signed in to change notification settings - Fork 12.8k
JS: Maximum call stack size exceeded at getTypeFromJSDocValueReference in 3.7.2 #34926
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I was able to reproduce with this code: /**
* @param {import('aws-sdk')} aws
*/
function test (aws) {} Something in the typings in aws-sdk (and others I assume) is causing this |
Experiencing similar, with slightly different callstack:
|
@RyanCavanaugh let's take this one for 3.7.3 too. Sounds like it breaks lighthouse and aws-sdk. |
Here's a self-contained repro: /** @param {import('./ex')} a */
function test(a) { } export var crash: {}; Notably, this does not crash: declare var nocrash: {}
export = nocrash; |
My previous fix for import types was too eager. The jsdoc-value-as-type fallback is only needed for import types followed by qualified names. |
TypeScript Version: 3.7.2, 3.8.0-dev.20191105
Search Terms:
JSDoc Type reference Maximum call stack size exceeded getTypeFromJSDocValueReference
Code
Unfortunately I don't have a small case test case yet. The easiest steps I have so far:
git clone https://github.com/GoogleChrome/lighthouse.git
cd lighthouse
yarn
yarn add -D [email protected]
yarn tsc
Expected behavior:
Complete
tsc
runActual behavior:
In
3.7.1-rc
there were many of theProperty 'methodName' does not exist on type 'typeof ClassName'
errors that were being worked on in #34671, but it looks like the fix(es) struggles with something in our dependency graph and/or styles of declarations.No issues or compilation errors using [email protected] (though we're fine if there are new errors exposed by 3.7 that will need to be fixed in our code :)
Related Issues:
This seems very related to the cluster of issues @sandersn was working on in #34671, #34707, #34685, and #34802
The text was updated successfully, but these errors were encountered: