Skip to content

Error: Debug Failure. False expression - 2.9.0-dev.20180420 #23588

Closed

Description

To access some of the newest JSDoc annotation support for webpack, I locally upgraded the newest nightly for typescript (see version below). However, I was coming across errors locally on my console (also seen below).

In addition, I have submitted a PR for webpack so our CI builds can fail and showcase this same failure (as it will run tsc --pretty there also). The PR is referenced also down below.

TypeScript Version: 2.9.0-dev.20180420

Expected behavior:
Running TSC with JSDoc annotations doesn't error.

Actual behavior:

> webpack@4.6.0 type-lint /Users/wecomm/Desktop/webpack
> tsc --pretty

/Users/wecomm/Desktop/webpack/node_modules/typescript/lib/tsc.js:62227
                throw e;
                ^

Error: Debug Failure. False expression.
    at Object.getJSDocHost (/Users/wecomm/Desktop/webpack/node_modules/typescript/lib/tsc.js:7787:18)
    at resolveEntityNameFromJSPrototype (/Users/wecomm/Desktop/webpack/node_modules/typescript/lib/tsc.js:22406:33)
    at resolveEntityName (/Users/wecomm/Desktop/webpack/node_modules/typescript/lib/tsc.js:22352:76)
    at resolveTypeReferenceName (/Users/wecomm/Desktop/webpack/node_modules/typescript/lib/tsc.js:26701:20)
    at getTypeFromTypeReference (/Users/wecomm/Desktop/webpack/node_modules/typescript/lib/tsc.js:26843:30)
    at checkTypeReferenceNode (/Users/wecomm/Desktop/webpack/node_modules/typescript/lib/tsc.js:37095:24)
    at checkSourceElement (/Users/wecomm/Desktop/webpack/node_modules/typescript/lib/tsc.js:39938:28)
    at checkSourceElement (/Users/wecomm/Desktop/webpack/node_modules/typescript/lib/tsc.js:39982:28)
    at checkJSDocParameterTag (/Users/wecomm/Desktop/webpack/node_modules/typescript/lib/tsc.js:37767:13)
    at checkSourceElement (/Users/wecomm/Desktop/webpack/node_modules/typescript/lib/tsc.js:3

Related Issues or PR's: webpack/webpack#7091

Activity

  1. mhegazy commented on Apr 20, 2018

    @mhegazy
    Contributor

    I beleive this is a duplicate of #23574 and should be addressed by #23575.

    Nathan Shively-Sanders (@sandersn) can you confirm please.

  2. TheLarkInn commented on Apr 20, 2018

    @TheLarkInn
    MemberAuthor

    Ahh sorry I missed the closed issues, thanks!

  3. sandersn commented on Apr 20, 2018

    @sandersn
    Member

    Yep, they are the same issue. Sorry about that.

  4. locked and limited conversation to collaborators on Jul 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    DuplicateAn existing issue was already created

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions