Outline error when opening a single file

Question

Outline error when opening a single file

aminya opened this issue 5 years ago · 12 comments

Outline error when opening a single file without a project:

Error: Error processing request. No Project.
Error: No Project.
    at Object.ThrowNoProject (C:\Users\yahyaaba\node_modules\typescript\lib\tsserver.js:137981:23)
    at IOSession.Session.getFileAndLanguageServiceForSyntacticOperation (C:\Users\yahyaaba\node_modules\typescript\lib\tsserver.js:145263:42)
    at IOSession.Session.getNavigationTree (C:\Users\yahyaaba\node_modules\typescript\lib\tsserver.js:145614:31)
    at Session.handlers.ts.createMapFromTemplate._a.(anonymous function) (C:\Users\yahyaaba\node_modules\typescript\lib\tsserver.js:144481:61)
    at C:\Users\yahyaaba\node_modules\typescript\lib\tsserver.js:146003:88
    at IOSession.Session.executeWithRequestId (C:\Users\yahyaaba\node_modules\typescript\lib\tsserver.js:145994:28)
    at IOSession.Session.executeCommand (C:\Users\yahyaaba\node_modules\typescript\lib\tsserver.js:146003:33)
    at IOSession.Session.onMessage (C:\Users\yahyaaba\node_modules\typescript\lib\tsserver.js:146027:35)
    at Interface.<anonymous> (C:\Users\yahyaaba\node_modules\typescript\lib\tsserver.js:147342:27)
    at Interface.emit (events.js:194:13)
    at Interface._onLine (readline.js:312:10)
    at Interface._normalWrite (readline.js:457:12)
    at Socket.ondata (readline.js:168:10)
    at Socket.emit (events.js:194:13)
    at addChunk (_stream_readable.js:296:12)
    at readableAddChunk (_stream_readable.js:277:11)
    at Socket.Readable.push (_stream_readable.js:232:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:165:17)
    at Callbacks.resolve (C:\Users\yahyaaba\.atom\packages\atom-typescript\dist\client\callbacks.js:40:28)
    at MessageStream.TypescriptServiceClient.onMessage (C:\Users\yahyaaba\.atom\packages\atom-typescript\dist\client\client.js:87:32)
    at MessageStream.emit (events.js:194:13)
    at addChunk (_stream_readable.js:296:12)
    at readableAddChunk (_stream_readable.js:277:11)
    at MessageStream.Readable.push (_stream_readable.js:232:10)
    at MessageStream.Transform.push (_stream_transform.js:148:32)
    at MessageStream._transform (C:\Users\yahyaaba\.atom\packages\atom-typescript\dist\client\client.js:212:22)
    at MessageStream.Transform._read (_stream_transform.js:187:10)
    at MessageStream.Transform._write (_stream_transform.js:175:12)
    at doWrite (_stream_writable.js:415:12)
    at writeOrBuffer (_stream_writable.js:399:5)
    at MessageStream.Writable.write (_stream_writable.js:299:11)
    at LineStream.ondata (_stream_readable.js:706:22)
    at LineStream.emit (events.js:194:13)
    at addChunk (_stream_readable.js:296:12)
    at readableAddChunk (_stream_readable.js:277:11)
    at LineStream.Readable.push (_stream_readable.js:232:10)
    at LineStream.Transform.push (_stream_transform.js:148:32)
    at LineStream._pushBuffer (C:\Users\yahyaaba\.atom\packages\atom-typescript\node_modules\byline\lib\byline.js:126:17)
    at LineStream._transform (C:\Users\yahyaaba\.atom\packages\atom-typescript\node_modules\byline\lib\byline.js:117:8)
    at LineStream.Transform._read (_stream_transform.js:187:10)
    at LineStream.Transform._write (_stream_transform.js:175:12)
    at doWrite (_stream_writable.js:415:12)
    at writeOrBuffer (_stream_writable.js:399:5)
    at LineStream.Writable.write (_stream_writable.js:299:11)
    at Socket.ondata (_stream_readable.js:706:22)
    at Socket.emit (events.js:194:13)
    at addChunk (_stream_readable.js:296:12)
    at readableAddChunk (_stream_readable.js:277:11)
    at Socket.Readable.push (_stream_readable.js:232:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:165:17) "C:\Users\yahyaaba\Documents\GitHub\JavaScript\atom-ide-datatip\typings\atom-ide.d.ts"

Answer 1 · 2020-07-08T04:52:38.000Z

I can't reproduce locally. This might be an issue with the custom TypeScript version you're using (apparently located in C:\Users\yahyaaba\node_modules\typescript\)

Answer 2 · 2020-07-08T08:03:49.000Z

Try opening a TS file from another project in the current project. The error is shown in the console.

Answer 3 · 2020-07-08T12:15:22.000Z

Still can't reproduce. You'll have to write a detailed reproduction guide I'm afraid. But the error is thrown by TypeScript server, not the package itself, it's only re-repored via console. So I still suspect the issue is your local TypeScript installation.

Answer 4 · 2020-10-07T00:06:59.000Z

This issue has been marked as stale because it did not have any activity for the last 90 days or more. Remove the stale label or comment or this will be closed in 14 days

Answer 5 · 2020-10-21T00:12:58.000Z

This is still an issue

Answer 6 · 2020-10-21T05:49:29.000Z

Well I still can't reproduce.

Answer 7 · 2020-10-21T06:18:30.000Z

I am not lying though 😄. I try to provide you a reproduction. Could you open the issue again?

Answer 8 · 2021-02-02T00:10:10.000Z

This issue has been marked as stale because it did not have any activity for the last 90 days or more. Remove the stale label or comment or this will be closed in 14 days

Answer 9 · 2021-02-02T01:13:31.000Z

Still an issue as I remember

Answer 10 · 2021-02-08T06:03:46.000Z

Probably related to atom-community/atom-languageclient#11

Answer 11 · 2021-02-10T13:50:29.000Z

Probably related to atom-community/atom-languageclient#11

Likely not, since atom-ts doesn't use atom-languageclient (can't, tsserver isn't LSP-compliant)

Answer 12 · 2021-05-27T00:28:43.000Z

This issue has been marked as stale because it did not have any activity for the last 90 days or more. Remove the stale label or comment or this will be closed in 14 days