cool intellisense in ide's and editor..yes I think is possible

Topics: General
Oct 3, 2012 at 5:10 AM

typescript looks great and promising but I think it can be successful only if it manages to convey the feeling about intellisense in other ide's and editors...specially for editors because many javascript developers use editor over ide' think it's possible, we can code scala inside sublime editor and emacs with type check and real autocomplete, ...


f# has a very cool project for intellisense in command line and actually this can be adapted for provide real intellisense in any editor or ide  (


Is possible than in a near future we've something similar to f# fsintellisense for typescript??...would be really amazing and a big plus for typescript  ....

Oct 4, 2012 at 10:30 PM

TypeScript comes with the language service in addition to the compiler (with the source under src/services). We'll be working to improve these as we go.

If there are specific features you'd like to add to the language service, let us know with a "feature request" in the issue tracker. 

Oct 5, 2012 at 12:33 PM

What would be really be great if the TypeScript playground editor was open-sourced. It should be relatively easy to run that editor into something like node-webkit and add some basic file/directory operations.

Than we would have an editor with intellisense capabilities written mainly in JavaScript (or even TypeScript, not sure if the playground editor itself was written in TypeScript).

Oct 7, 2012 at 8:40 PM

I just hacked together basic TypeScript support for SublimeLinter (thus only error-checking, but better than nothing).

Emphasis on "hacked" - it is probably still buggy, but I wanted it out in the open so others can contribute. Here is the according SublimeLinter pull-request.

I welcome anybody to improve the code!

Oct 9, 2012 at 8:45 PM


I've created a new CodeMirror mode for TypeScript.

It's a pity that Microsoft does not want to release the playground editor but nothing stops us from building our own small editor:

Feel free to make pull requests, to fork the code or to tell any suggestions!

Nov 12, 2012 at 11:18 AM


I wrote auto-complete source for emacs using the language service.

Nov 15, 2012 at 6:41 PM
Edited Nov 15, 2012 at 6:43 PM

@k_matsuzaki: thanks!

That is very useful also for non-emacs efforts, because it pulls together most of the relevant pieces in one commandline tool (isense.ts). It is a commandline client for the language services and harness, outputting info in JSON format for editors to consume.

Notes to typescript project:

a) the particulars of output format might differ for different consumers (ides, editors), but for documentation purposes, it would be very helpful if a commandline service client like isense.ts would be included in the main typescript repo.

b) there are some very odd things going on in typescript's standard harness.ts:

1 instead of relying on normal module system import, it tries to guess the path to typescriptServices.js and eval that source directly

2 it also tries to guess the path to lib.d.ts

Both guesses go wrong if one tries to generate an all-in-one .js somewhere outside the typescript repo. The workarounds, included in auto-complete-ts's modified harness.ts seem to be simply to comment out the eval code and to inject the lib.d.ts path explicitly. Could these please be addressed in the original harness.ts source?

c) OptionsParser hardcodes the command name (tsc), interfering with reuse for other commandline tools.

Note for auto-complete-ts: parse should use a different pattern for result matching - at least allowing for double quotes "result" ;-)

Nov 25, 2012 at 2:44 AM


I fixed it, now parse json and get result.

TypeScript.el: I need major-mode hook like

Nov 25, 2012 at 8:24 AM

Readers of this thread will also find the thread TypeScript Editor interesting. There's a CodeMirror/node-webkit-based TS editor, and there's a commandline server for the TS language services, and there's a Vim plugin using the latter (all experimental/early stage;-).

@k_matsuzaki: you might want to reuse some ideas from that thread for your emacs service:

- using the real language service, and removing the test/shim-related code from harness

- using dependency resolution from tsc

- using a commandline server, to share slow project loading time over many fast queries

I'm hoping that -once things get more stable- the TS server can be re-used for TS modes in other editors.