TypeError: Cannot read property 'kind' of undefined #38383

Activity

1. Jessidhia commented on May 7, 2020

   

   Jessica Franco (Jessidhia)

   on May 7, 2020

   Last edited by Jessidhia

   Author

   More actions

   Adding a console.log to createDiagnosticForNode with all its arguments prints the following:

   undefined {
     code: 6203,
     category: 3,
     key: '_0_was_also_declared_here_6203',
     message: "'{0}' was also declared here.",
     reportsUnnecessary: undefined,
     elidedInCompatabilityPyramid: undefined
   } undefined globals undefined undefined undefined
   

   nitpick: it's spelled "compatibility"
2. Jessidhia commented on May 7, 2020

   

   Jessica Franco (Jessidhia)

   on May 7, 2020

   Last edited by Jessidhia

   Author

   More actions

   It looks like the line that is causing the crash itself is:

   // @ts-check
   // this is a jest.config.js file
   
   const config = makeConfig(/* ... */)
   
   config.globals.__STORYBOOK__ = false // this line
   // commenting it out prevents the crash
   
   module.exports = config

   where the return type of makeConfig is import('@jest/types').Config.InitialOptions.
3. Ryan Cavanaugh (RyanCavanaugh)

   added

   BugA bug in TypeScriptA bug in TypeScript

   on May 8, 2020
4. Ryan Cavanaugh (RyanCavanaugh)

   assigned

   Eli Barzilay (elibarzilay)

   on May 8, 2020
5. Ryan Cavanaugh (RyanCavanaugh)

   added this to the TypeScript 4.0 milestone on May 8, 2020
6. Multiply commented on May 13, 2020

   

   Jens Fosgerau (Multiply)

   on May 13, 2020

   More actions

   We're seeing a similar issue, however, I can't seem to find the cause in our code.

   Jessica Franco (@Jessidhia) did you add more console.log's in other parts to find the file/line?
7. lukaskl commented on May 13, 2020

   

   Lukas Klusis (lukaskl)

   on May 13, 2020

   Last edited by lukaskl

   More actions

   I've noticed quite similar (also, looking from stack trace - seemingly different one) issue. I thought that I will better file it as a dedicated issue - #38558. If it will turn out, that it is a duplicate, we can simply close the issue.
8. elibarzilay commented on May 18, 2020

   

   Eli Barzilay (elibarzilay)

   on May 18, 2020

   Contributor

   More actions

   Jessica Franco (@Jessidhia), can you post a precise repro? I tried a few things with the above snippet but can't get it to happen.
9. Eli Barzilay (elibarzilay)

   added

   Awaiting More FeedbackThis means we'd like to hear from more people who would be helped by this featureThis means we'd like to hear from more people who would be helped by this feature

   on May 18, 2020
10. pferdone commented on May 19, 2020

    

    pferdone

    on May 19, 2020

    More actions

    Eli Barzilay (@elibarzilay) this happened to me today as I was setting up a new nextjs project. Basically if your checkout this example or yarn create next-app --example custom-server-typescript custom-server-typescript-app and run yarn dev you get this error:

        TypeError: Cannot read property 'kind' of undefined
            at getErrorSpanForNode (../node_modules/typescript/lib/typescript.js:13856:22)
            at createDiagnosticForNodeInSourceFile (../node_modules/typescript/lib/typescript.js:13805:20)
            at Object.createDiagnosticForNode (../node_modules/typescript/lib/typescript.js:13796:16)
            at ../node_modules/typescript/lib/typescript.js:41824:135
            at Map.forEach (<anonymous>)
            at getInitializerTypeFromAssignmentDeclaration (../node_modules/typescript/lib/typescript.js:41806:52)
            at getWidenedTypeForAssignmentDeclaration (../node_modules/typescript/lib/typescript.js:41700:123)
            at getTypeOfFuncClassEnumModuleWorker (../node_modules/typescript/lib/typescript.js:42260:34)
            at getTypeOfFuncClassEnumModule (../node_modules/typescript/lib/typescript.js:42239:51)
            at getTypeOfSymbol (../node_modules/typescript/lib/typescript.js:42352:24)
            at checkPropertyAccessExpressionOrQualifiedName (../node_modules/typescript/lib/typescript.js:57154:53)
            at checkPropertyAccessExpression (../node_modules/typescript/lib/typescript.js:57013:17)
            at checkExpressionWorker (../node_modules/typescript/lib/typescript.js:61646:28)
            at checkExpression (../node_modules/typescript/lib/typescript.js:61567:38)
            at maybeCheckExpression (../node_modules/typescript/lib/typescript.js:60780:34)
            at checkBinaryExpression (../node_modules/typescript/lib/typescript.js:60737:25)
    

    If you pin Typescript to 3.8.3 the error goes away. Cheers

    👍React with 👍5Reacted by na2hiro, Cher Igor, kendo-leadlab, Harry Robbins and Aravinda

    👎React with 👎2Reacted by chenwenqin and Dmitri Russu
11. elibarzilay commented on May 19, 2020

    

    Eli Barzilay (elibarzilay)

    on May 19, 2020

    Contributor

    More actions

    I'm not sure if I'm doing it right, but I tried the following two chunks in an empty directory:

    $ git clone https://github.com/zeit/next.js
    $ cd next.js/examples/custom-server-typescript
    $ npm i
    $ tsc
    

    and

    $ yarn create next-app --example custom-server-typescript custom-server-typescript-app
    $ cd custom-server-typescript-app
    $ yarn dev
    

    Both ran without any errors...
12. Multiply commented on May 19, 2020

    

    Jens Fosgerau (Multiply)

    on May 19, 2020

    More actions

    Eli Barzilay (@elibarzilay) try to change the typescript version to the latest in package.json before installing.
13. pferdone commented on May 20, 2020

    

    pferdone

    on May 20, 2020

    Last edited by pferdone

    More actions

    Eli Barzilay (@elibarzilay) Jens Fosgerau (@Multiply) yeah, it installs Typescript 3.9.3 when I setup the project. I get the error described above and as I said when I switch to 3.8.3 the error goes away.
14. elibarzilay commented on May 20, 2020

    

    Eli Barzilay (elibarzilay)

    on May 20, 2020

    Contributor

    More actions

    I'm using a tsc which is wired to a build from the current master, but just in case, I repeated both of the above after editing package.json and removed the TS line, and repeated with editing it to 3.9.3.

    Still no errors...
15. elibarzilay commented on May 21, 2020

    

    Eli Barzilay (elibarzilay)

    on May 21, 2020

    Contributor

    More actions

    To make this more controllable, I used docker. This is my build file (which doesn't get any errors):

    FROM ubuntu
    
    RUN apt update \
     && apt upgrade -y \
     && apt install -y curl
    
    RUN curl -sL https://deb.nodesource.com/setup_14.x | bash - \
     && apt install -y nodejs
    
    RUN curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - \
     && echo "deb https://dl.yarnpkg.com/debian/ stable main" >> /etc/apt/sources.list \
     && apt update && apt install -y yarn
    
    RUN mkdir /work
    WORKDIR /work
    
    RUN yarn create next-app --example custom-server-typescript t \
     && cd t \
     && sed -i -e 's/\("typescript": "^\)\(.*\)"/\13.9.3"/' package.json
    
16. 14 remaining items

    Load more
17. Eli Barzilay (elibarzilay)

    removed

    Needs More InfoThe issue still hasn't been fully clarifiedThe issue still hasn't been fully clarified

    on Jun 4, 2020
18. Eli Barzilay (elibarzilay)

    added a commit that references this issue on Jun 4, 2020

    Fix merging of JS value & TS type decl

    ...

    This issue will close once commit 5b8f043 is merged into the 'main' branch.

    5b8f043
19. Eli Barzilay (elibarzilay)

    closed this as completedin #38936on Jun 4, 2020
20. Eli Barzilay (elibarzilay)

    added a commit that references this issue on Jun 4, 2020

    Fix merging of JS value & TS type decl

    ...

    This issue will close once commit 4ee013d is merged into the 'main' branch.

    4ee013d
21. Multiply commented on Jun 18, 2020

    

    Jens Fosgerau (Multiply)

    on Jun 18, 2020

    More actions

    Bit late with the response, sorry.
    After applying your patch locally the issue went away for us. (eagerly waiting for it to be included in a release)
22. CherIgor commented on Jun 19, 2020

    

    Cher Igor (CherIgor)

    on Jun 19, 2020

    Last edited by CherIgor

    More actions

    Had the fix been released? I still have the same issue with latest: next 9.4.4, typescript 3.9.5 and ts-node 8.10.2. node -v 12.4.0.
    The same as was mentioned previously: switching to typescript 3.8.3 fixes the problem.

    👍React with 👍18Reacted by barbara-lea, Nyx, Matteo Antoci, Yui Ichioka, Martin Reichl, Tanner Krewson, Sebastian Di Luzio, Daniel Sousa, Kevin Peters, jarda-svoboda and 8 more

    👀React with 👀8Reacted by Sean Rankin, barbara-lea, Tanner Krewson, Kevin Peters, Eric Juta, Sourabh Singh, Amirhosein Esmaily and p-null
23. purplesyringa commented on Jul 20, 2020

    

    Alisa Sireneva (purplesyringa)

    on Jul 20, 2020

    More actions

    This is still a problem with TypeScript 3.9.7. Eli Barzilay (@elibarzilay)'s repro fails without any modifications. Unfortunately downgrading 3.8.3 is not an option for me because old versions ironically have another bug. Will we get this problem fixed?

    👍React with 👍13Reacted by Seyed Alireza Fatemi Jahromi, barbara-lea, Ruslan Baigunussov, Matthias Prieth, Nafis, Sourabh Singh, Tanner Krewson, Henry S Hunt, PiotrGrzy, Artur Kurowski and 3 more

    😄React with 😄2Reacted by Nelson Sandoval and gekkedev
24. sourabh8003 commented on Jul 26, 2020

    

    Sourabh Singh (sourabh8003)

    on Jul 26, 2020

    Last edited by sourabh8003

    More actions

    Eli Barzilay (@elibarzilay) Hi, Downgrading the TypeScript version from latest to 3.8.3 solves the problem but downgrading TS version is not a good option for me as well. Can we expect a fix for this?

    👍React with 👍3Reacted by Tanner Krewson, Henry S Hunt and Nelson Sandoval
25. henhen724 commented on Jul 27, 2020

    

    Henry S Hunt (henhen724)

    on Jul 27, 2020

    More actions

    Having the same issue with nextJS version 9.4.4 with Typescript version 3.9.7.
26. elibarzilay commented on Jul 29, 2020

    

    Eli Barzilay (elibarzilay)

    on Jul 29, 2020

    Contributor

    More actions

    Sourabh Singh (@sourabh8003) IIRC, it was only included in 4.0.

    👍React with 👍2Reacted by Sourabh Singh and Jinyoung Lee
27. henhen724 commented on Jul 29, 2020

    

    Henry S Hunt (henhen724)

    on Jul 29, 2020

    More actions

    Sorry, I should have read more carefully. It's working on 4.0.0-dev.20200729. Thank you.

    👍React with 👍1Reacted by khuongphp
28. SurjitSahoo commented on May 30, 2021

    

    Surjit Sahoo (SurjitSahoo)

    on May 30, 2021

    More actions

    I am still having this issue on node 14.17.0, typescript 4.2.4, ts-node 9.0.0

    TypeDoc exiting with unexpected error:
    TypeError: Cannot read property 'kind' of undefined
        at Object.isDeclaration (/home/surjit/practice/ds_algo/DataStructures-Algorithms/node_modules/typescript/lib/typescript.js:13449:18)
        at Object.isDeclarationName (/home/surjit/practice/ds_algo/DataStructures-Algorithms/node_modules/typescript/lib/typescript.js:16414:75)
        at getTypeOfSymbolAtLocation (/home/surjit/practice/ds_algo/DataStructures-Algorithms/node_modules/typescript/lib/typescript.js:66938:20)
        at Object.getTypeOfSymbolAtLocation (/home/surjit/practice/ds_algo/DataStructures-Algorithms/node_modules/typescript/lib/typescript.js:45176:35)
        at Object.convertProperty (/home/surjit/practice/ds_algo/DataStructures-Algorithms/node_modules/typedoc/dist/lib/converter/symbols.js:330:176)
        at convertSymbol (/home/surjit/practice/ds_algo/DataStructures-Algorithms/node_modules/typedoc/dist/lib/converter/symbols.js:80:79)
        at convertSymbols (/home/surjit/practice/ds_algo/DataStructures-Algorithms/node_modules/typedoc/dist/lib/converter/symbols.js:86:9)
        at Object.convertClassOrInterface (/home/surjit/practice/ds_algo/DataStructures-Algorithms/node_modules/typedoc/dist/lib/converter/symbols.js:264:5)
        at Object.convertSymbol (/home/surjit/practice/ds_algo/DataStructures-Algorithms/node_modules/typedoc/dist/lib/converter/symbols.js:80:79)
        at Converter.convertExports (/home/surjit/practice/ds_algo/DataStructures-Algorithms/node_modules/typedoc/dist/lib/converter/converter.js:182:23)
    npm ERR! code ELIFECYCLE
    npm ERR! errno 5
    npm ERR! [email protected] docs: `typedoc --options tsdoc.json --plugin typedoc-plugin-extras --favicon docs/favicon.png`
    npm ERR! Exit status 5
    npm ERR! 
    npm ERR! Failed at the [email protected] docs script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    
29. hadnet commented on May 31, 2021

    

    hadnet (hadnet)

    on May 31, 2021

    Last edited by hadnet

    More actions

    Same thing here, Surjit Sahoo (@SurjitSahoo) . Previously it was working fine, but now throws that error. Did you find out a solution?
    NOTE: My package.json got updated to TS 4.2.4 (cause the ^) and thus the error (some issue with that version I guess..). Editing TS to 4.2 it seems to work fine now.

    👍React with 👍2Reacted by Surjit Sahoo and Sebastian Malton
30. Nokel81 commented on Jun 2, 2021

    

    Sebastian Malton (Nokel81)

    on Jun 2, 2021

    More actions

    I see this running typedoc on typescript 4.3.2 too

    👍React with 👍10Reacted by Kyℓe Hensel, Laurens D'Hondt, mikeevstropov, Benjamin Ashbaugh, Francesco Gatti, Alireza , gxmzjxk, Rachita Bansal, Carter and xorbious

    👀React with 👀1Reacted by Benjamin Ashbaugh
31. microsoft

    locked as resolved and limited conversation to collaborators on Oct 21, 2025