{"action":"created","issue":{"url":"https://api.github.com/repos/Microsoft/nodejstools/issues/613","labels_url":"https://api.github.com/repos/Microsoft/nodejstools/issues/613/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/nodejstools/issues/613/comments","events_url":"https://api.github.com/repos/Microsoft/nodejstools/issues/613/events","html_url":"https://github.com/Microsoft/nodejstools/issues/613","id":118277567,"number":613,"title":"New ES6 intellisense","user":{"login":"SteveALee","id":618922,"avatar_url":"https://avatars.githubusercontent.com/u/618922?v=3","gravatar_id":"","url":"https://api.github.com/users/SteveALee","html_url":"https://github.com/SteveALee","followers_url":"https://api.github.com/users/SteveALee/followers","following_url":"https://api.github.com/users/SteveALee/following{/other_user}","gists_url":"https://api.github.com/users/SteveALee/gists{/gist_id}","starred_url":"https://api.github.com/users/SteveALee/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SteveALee/subscriptions","organizations_url":"https://api.github.com/users/SteveALee/orgs","repos_url":"https://api.github.com/users/SteveALee/repos","events_url":"https://api.github.com/users/SteveALee/events{/privacy}","received_events_url":"https://api.github.com/users/SteveALee/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-11-22T17:56:57Z","updated_at":"2015-11-23T10:04:29Z","closed_at":null,"body":"I'm using node 4.x.x and the built in [ES6 features](https://nodejs.org/en/docs/es6/) like `const` and template strings. Currently this seems to be unsupported in intellisense\r\n\r\n1) The maximum intellisense option doesn't recognise `const` and highlights ` as an error\r\n2) The ES6 intellisense support appears to just show 'any' for everything.\r\n\r\nThe problem with adding Definitely Typed definitions is they are community maintained For Hapi the file is very out of date so not really much use. Plus it's a real pain to manually insert and manage the references in each file.\r\n\r\nI think an approach that supports ES6 without manual management of definitely Type refs is required. "},"comment":{"url":"https://api.github.com/repos/Microsoft/nodejstools/issues/comments/158892791","html_url":"https://github.com/Microsoft/nodejstools/issues/613#issuecomment-158892791","issue_url":"https://api.github.com/repos/Microsoft/nodejstools/issues/613","id":158892791,"user":{"login":"SteveALee","id":618922,"avatar_url":"https://avatars.githubusercontent.com/u/618922?v=3","gravatar_id":"","url":"https://api.github.com/users/SteveALee","html_url":"https://github.com/SteveALee","followers_url":"https://api.github.com/users/SteveALee/followers","following_url":"https://api.github.com/users/SteveALee/following{/other_user}","gists_url":"https://api.github.com/users/SteveALee/gists{/gist_id}","starred_url":"https://api.github.com/users/SteveALee/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SteveALee/subscriptions","organizations_url":"https://api.github.com/users/SteveALee/orgs","repos_url":"https://api.github.com/users/SteveALee/repos","events_url":"https://api.github.com/users/SteveALee/events{/privacy}","received_events_url":"https://api.github.com/users/SteveALee/received_events","type":"User","site_admin":false},"created_at":"2015-11-23T10:04:29Z","updated_at":"2015-11-23T10:04:29Z","body":"Are you suggesting the need for explicitly DT refs will removed in time? That requirement is bit of  deal breaker for me. I seem to recall @code required them in the first release but it may have been removed later?\r\n\r\nI fully agree with the desire to collaborate with other efforts in this area. But, I'd like to avoid the extra work of managing explicit DT refs, especially as I tend to have many small source files\r\n\r\nCan you point me at good introductory docs for the new TS intellisense? I've been trying it with more substantial code and am seeing more useful intellisense now. However, there's still lots of unknowns and 'any's compared with the full NTVS intellisense.\r\n\r\nIf it's faster that will be a boost, though latest full NTVS intellisense is pretty good now.\r\n\r\nThe ability to browse using the top combos is a nice extra.\r\n\r\n"}}