I'm not sure what I did to trigger this. I was editing a JavaScript file, then left Atom open while doing other stuff on my computer, then tried to type in the JavaScript file.

/cc @damieng

Atom: 1.22.0-dev-38d9c07 x64 Electron: 1.6.9 OS: Mac OS X 10.11.6 Thrown From: ide-typescript package 0.1.6

Stack Trace

Uncaught Error: Connection is closed.

At /Users/max/.atom/packages/ide-typescript/node_modules/vscode-jsonrpc/lib/main.js:604

Error: Connection is closed.
    at /packages/ide-typescript/node_modules/vscode-jsonrpc/lib/main.js:129:28)
    at throwIfClosedOrDisposed (/packages/ide-typescript/node_modules/vscode-jsonrpc/lib/main.js:604:19)
    at Object.sendNotification (/packages/ide-typescript/node_modules/vscode-jsonrpc/lib/main.js:658:13)
    at LanguageClientConnection._sendNotification (/packages/ide-typescript/node_modules/atom-languageclient/build/lib/languageclient.js:233:15)
    at LanguageClientConnection.didChangeTextDocument (/packages/ide-typescript/node_modules/atom-languageclient/build/lib/languageclient.js:126:10)
    at TextEditorSyncAdapter.sendFullChanges (/packages/ide-typescript/node_modules/atom-languageclient/build/lib/adapters/document-sync-adapter.js:196:22)
    at Function.module.exports.Emitter.simpleDispatch (/Applications/Atom.app/Contents/Resources/app/node_modules/event-kit/lib/emitter.js:25:20)
    at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app/node_modules/event-kit/lib/emitter.js:141:34)
    at /Applications/Atom.app/Contents/Resources/app/src/text-editor.js:626:38
    at Function.module.exports.Emitter.simpleDispatch (/Applications/Atom.app/Contents/Resources/app/node_modules/event-kit/lib/emitter.js:25:20)
    at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app/node_modules/event-kit/lib/emitter.js:141:34)
    at DisplayLayer.emitDidChangeSyncEvent (/Applications/Atom.app/Contents/Resources/app/node_modules/text-buffer/lib/display-layer.js:823:24)
    at /Applications/Atom.app/Contents/Resources/app/node_modules/text-buffer/lib/text-buffer.js:757:35
    at Map.forEach (native)
    at TextBuffer.module.exports.TextBuffer.emitDidChangeEvent (/Applications/Atom.app/Contents/Resources/app/node_modules/text-buffer/lib/text-buffer.js:756:47)
    at TextBuffer.module.exports.TextBuffer.applyChange (/Applications/Atom.app/Contents/Resources/app/node_modules/text-buffer/lib/text-buffer.js:739:18)
    at TextBuffer.module.exports.TextBuffer.revertToCheckpoint (/Applications/Atom.app/Contents/Resources/app/node_modules/text-buffer/lib/text-buffer.js:946:22)
    at TextBuffer.module.exports.TextBuffer.transact (/Applications/Atom.app/Contents/Resources/app/node_modules/text-buffer/lib/text-buffer.js:897:20)
    at TextEditor.module.exports.TextEditor.transact (/Applications/Atom.app/Contents/Resources/app/src/text-editor.js:1673:32)
    at /Applications/Atom.app/Contents/Resources/app/src/text-editor.js:1234:30
    at TextEditor.module.exports.TextEditor.mergeSelections (/Applications/Atom.app/Contents/Resources/app/src/text-editor.js:2617:49)
    at TextEditor.module.exports.TextEditor.mergeIntersectingSelections (/Applications/Atom.app/Contents/Resources/app/src/text-editor.js:2583:41)
    at TextEditor.module.exports.TextEditor.mutateSelectedText (/Applications/Atom.app/Contents/Resources/app/src/text-editor.js:1232:25)
    at TextEditor.module.exports.TextEditor.insertText (/Applications/Atom.app/Contents/Resources/app/src/text-editor.js:1198:25)
    at TextEditor.object.(anonymous function) [as insertText] (/Applications/Atom.app/Contents/Resources/app/node_modules/underscore-plus/lib/underscore-plus.js:77:33)
    at TextEditorComponent.didTextInput (/Applications/Atom.app/Contents/Resources/app/src/text-editor-component.js:1626:28)

Commands

     -0:10 editor:move-to-first-character-of-line (input.hidden-input)
     -0:09.8.0 editor:cut-to-end-of-line (input.hidden-input)
  2x -0:02.6.0 core:move-up (input.hidden-input)
  3x -0:02.1.0 core:move-right (input.hidden-input)

Non-Core Packages

atom-ide-ui 0.2.0 
autocomplete-clang 0.11.3 
git-pear 1.2.1 
ide-flowtype 0.14.0 
ide-typescript 0.1.6 
journal 0.1.1 
language-typescript-grammars-only 1.6.0 
linter 2.2.0 
linter-clang 4.1.2 
minimap 4.29.6 
racer 0.20.0 
real-time 0.1.0 
sort-lines 0.15.0 
toggle-quotes 1.0.1 

Has it ever been considered to switch away from SourceGraph? I was unable to use this plugin due to having symlink cycles (because I'm using lerna) and my understanding is that the SourceGraph team does not want to support this use case. I feel like in a lot of projects this leaves the plugin completely broken and infinitely using CPU until the process runs out of memory.

As a proof of concept I forked this repo and used Theia Language Server which at the moment seems to be a bit better maintained. My proof of concept is up at https://github.com/mattlyons0/ide-typescript-theia ~~(and does have a few rough edges, on my Mac the tsserver is failing to find node on startup (which can be solved by toggling the plugin disabled then enabled after startup) but its working fine on my Linux box).~~ (fixed in https://github.com/theia-ide/typescript-language-server/pull/88 ) It seems to have better performance, no more infinite loops and a bit better feature support than SourceGraph (formatting hook is supported). ~~The only downside I found is that the outline is no longer a tree but all on the same level, I'm not quite sure why this is (or how the tree is generated) but the responses to textDocument/documentSymbol after a brief investigation seemed to be identical.~~ This has been fixed upstream: https://github.com/theia-ide/typescript-language-server/pull/69

In summary I'm wondering if you have considered switching to a different Language Server, especially given how easy it is and the issues that have been cropping up with SourceGraph: #70 #95 #113 to name a few... Also I've noticed that hyperclicking into definition files actually works and doesn't open a broken URL which is a plus. All in all I feel the Theia Language Server has been rock solid and solves many issues with the current SourceGraph Server.

Wher I can set this option? Experimental support for decorators is a feature that is subject to change in a future release. Set the ‘experimentalDecorators’ option to remove this warning.

One of the things that I had used before the ide package was an eslint package that would fix many basic problems on file save (whitespace, some other things, can't remember now what else). This was incompatible with the ide-typescript package (was it eslint?), but i'd be curious if similar functionality was coming to the core ide-typescript package, or there are other packages that make good compliments to this package.

I'll hang up and listen ;)

A few things to know before you create an issue

• This package requires Atom 1.21
• We launch a "language server" process on your machine that understands the language you are editing
• What that server can do - syntax compatibility, whether it supports formatting or outlines etc - is outside of our control
• You can see what the language server supports by checking out our README and following the link after "powered by"
• "disconnected", "JSONRPC" or "Content-Header" errors indicate that server process died. We're working on better recovery right now

If you have understood all this, please remove this text and start writing your issue :)

After updating the package to the latest version, 0.7.3, everytime I type a space or colon character in a .js file, I start to see irrelevant suggestions for things like SVGFEFuncBElement or SVGFEMergeNodeElement (see image below). This makes the editor unusable since everytime I do a space, colon, or semi-colon character followed by a return, I will accidentally choose an autocompleted snippet I don’t want.

My installed snippets no longer show up at the top. Instead, the show up at the bottom of the autocompletion list or not at all. Disabling ide-typescript returns behavior to the normal, expected behavior.

If I downgrade ide-typescript to 0.7.2 by running apm uninstall ide-typescript and then apm install [email protected], then my snippets and autocompletions show up as expected again (see image below). I am not sure what the cause of this is.

Related issues: #91

I installed this package via apm install atom/ide-typescript

I am not sure how to start the language server or even know if it's working .

Could you please provide some insight on what to expect and how to determine if the service is working properly.

My tsconfig.json has compilerOptions.jsx="react" that comes from an "extends" property. I'm seeing this error.

{
  "extends": "./node_modules/[buildsystempackage]/tsconfig.json",
   ...
}

I keep getting the same issue when I try to update ide-typescript to version 0.6.1. EBUSY: resource busy or locked, rmdir 'C:\Users\Cruckshank\.atom\packages\ide-typescript' I'm using Atom version 1.12.0-beta0

Hi, is there any doc explaining how the compilation works? In my project "tsc" return no error. ide-typescript finds hundreds of errors. It looks like it is using some outdated Typescript version. Can this be somehow configured?

I even got error on "import * as React from 'react';" - File '/Users/tomi/Github/packages/webpack2-typescript-2/node_modules/@types/react/index.d.ts' is not a module.

But overall the first look is impressive!

I'm using this server to get just the JavaScript features and have the flow server installed as well. I'm getting errors about defining flow types in my JS files. There should be some better detection of typescript before it applies the linting rule.

Prerequisites

• [x] Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode N/A
  • Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages N/A

Description

The setting "Enable Atom-Typescript for JavaScript files (experimental)" will not disable such that the setting is remembered after a reset.

Steps to Reproduce

1. Click to get the setting "Enable Atom-Typescript for JavaScript files (experimental)" unchecked.
2. Restart Atom.

Expected behavior:

See that the setting is not in effect and "Enable Atom-Typescript for JavaScript files (experimental)" remains unchecked after the restart.

Actual behavior:

The setting is still in effect (and "Enable Atom-Typescript for JavaScript files (experimental)" is checked again.)

Reproduces how often:

100%

Versions

Atom : 1.51.0-beta0 Electron: 5.0.13 Chrome : 73.0.3683.121 Node : 12.0.0

apm 2.5.0 npm 6.14.5 node 10.20.1 x64 atom 1.51.0-beta0 python 2.7.15 git 2.21.0

Additional Information

N/A

First, thanks to the developers of this great package ide-typescript. It is great alongside atom-ide-ui package. However, I've discovered that ide-typescript is interfering in autocomplete-plus package, causing this last one to not show suggestions of common words already typed in the code. For example, if I have typed the term "student" in the code or in comments and retype the same word, the autocompletion is not showing the related suggestion when ide-typescript package is activated. So, in order to to have back the autocomplete service in a full way I have to deactivate the ide-typescript, what is really sad.

Hello,

I'd love to have a feature called "compileOnSave". Currently, I have to launch a separate Terminal window and call tsc -w in my project and that's a bummer in a way. tsconfig.json Allows IDEs to check for that attribute and act accordingly:

• current schema for tsconfig
• official docs

I know that atom-typescript supports it and it looks like WebStorm does to. I wonder how hard it would be to implement it. If it's easy enough, I'd try it anyway.

What are your thoughts on this?

When ide-vue and ide-typescript are used together, intellisense javascript support is in .js files but not in .vue, if desative the ide-typescript package would have support again for .vue but not for javascript, some recommendation on this ?? it is uncomfortable when working with nodejs to activate one package and then the other but when I work on both at the same time nodejs and vue there is where the problem is real, thanks for everything

After updating to 0.8.0 I'm really happy with the new language server and expanded diagnostics, but I'm getting a type of warning while working in JavaScript specific to TypeScript.

For example:

const nodemailer = require('nodemailer');

The base package for Nodemailer doesn't have an implementation for TypeScript, which I assume triggers this warning:

Could not find a declaration file for module 'nodemailer'. 'c:/###/node_modules/nodemailer/lib/nodemailer.js' implicitly has an 'any' type. Try npm install @types/nodemailer if it exists or add a new declaration (.d.ts) file containing `declare module 'nodemailer';

This occurs with several packages including ffmpeg-static, child-process-promise, and others.

I'm not aware of any way to set up configuration for the new language server, but adding a way to suppress specific warnings like these would be really helpful, similar to eslint's config. Or at the very least, maybe a simple filter before the linter warnings are consumed?