rust-analyzer - [FORK] modified to work on wasm targets

	Commit message (Collapse)	Author	Age	Files	Lines
...
*	Remove prettier	Aleksey Kladov	2019-12-30	1	-6/+0
\|
*	Add prettier	Aleksey Kladov	2019-12-30	1	-0/+6
\|
*	Add rollup	Aleksey Kladov	2019-12-30	1	-17/+709
\|
*	Minimize TypeScript build	Aleksey Kladov	2019-12-30	1	-1675/+0
\|
*	Fix ↵	Seivan Heidari	2019-12-23	1	-0/+5
\| \| \| \| \| \|	https://github.com/rust-analyzer/rust-analyzer/pull/2061#discussion_r348716036 Fix https://github.com/rust-analyzer/rust-analyzer/pull/2061/files/68a5ff050faf514e9d122212a66703ca8ce66ab7#r361019340
*	Update to latest packages	kjeremy	2019-12-20	1	-25/+25
\|
*	use pretter settings in ts-lint	Edwin Cheng	2019-12-17	1	-0/+39
\|
*	Add rollup sourcemap and fix launch.json	Edwin Cheng	2019-12-08	1	-0/+53
\|
*	Code: bump deps	Laurențiu Nicola	2019-12-08	1	-399/+232
\|
*	Code: check whether the LSP binary is in PATH	Laurențiu Nicola	2019-12-08	1	-0/+5
\|
*	Fix npm vulnerability warning	Edwin Cheng	2019-12-06	1	-3/+3
\|
*	Bump rollup and vsce	kjeremy	2019-10-10	1	-27/+19
\|
*	add rollup bundler for vscode extension	JasperDeSutter	2019-09-23	1	-15/+175
\|
*	Switch to `@types/vscode` and `vscode-test`	Bastian Köcher	2019-08-26	1	-423/+723
\| \| \| \| \| \|	The old `vscode` package is outdated and it is recommened to switch to these two new packages. This also solves a problem of a missing `.d.ts` for `vscode` in Nixos.
*	:arrow_up: npm	Aleksey Kladov	2019-07-29	1	-104/+93
\|
*	:arrow_up: npm deps	Aleksey Kladov	2019-07-25	1	-9/+9
\|
*	Bump lodash from 4.17.11 to 4.17.14 in /editors/code	dependabot[bot]	2019-07-12	1	-3/+3
\| \| \| \| \| \| \|	Bumps [lodash](https://github.com/lodash/lodash) from 4.17.11 to 4.17.14. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](https://github.com/lodash/lodash/compare/4.17.11...4.17.14) Signed-off-by: dependabot[bot] <[email protected]>
*	Update vsce to latest	kjeremy	2019-07-03	1	-40/+41
\|
*	Semantic highlighting spike	Pascal Hertleif	2019-05-27	1	-0/+10
\| \| \| \| \| \| \| \| \| \|	Very simple approach: For each identifier, set the hash of the range where it's defined as its 'id' and use it in the VSCode extension to generate unique colors. Thus, the generated colors are per-file. They are also quite fragile, and I'm not entirely sure why. Looks like we need to make sure the same ranges aren't overwritten by a later request?
*	:arrow_up: code	Aleksey Kladov	2019-04-21	1	-1432/+175
\|
*	Add proper process teminate method	Edwin Cheng	2019-04-02	1	-0/+51
\|
*	Update dependencies	DJMcNab	2019-02-10	1	-6/+6
\|
*	Add support for a seperate output channel for trace messages	DJMcNab	2019-02-10	1	-7/+7
\|
*	Update npm packages	kjeremy	2019-02-07	1	-92/+58
\|
*	Address issues flagged in review	Marcus Klaas de Vries	2019-01-19	1	-45/+45
\|
*	Add additional pattern variants	Marcus Klaas de Vries	2019-01-19	1	-45/+45
\|
*	:arrow_up: npm	Aleksey Kladov	2019-01-13	1	-66/+66
\|
*	index stuff produced by macros	Aleksey Kladov	2019-01-03	1	-436/+436
\|
*	Reload package-lock.json	DJMcNab	2018-12-19	1	-72/+78
\|
*	use new clear-terminal feature	Aleksey Kladov	2018-12-15	1	-11/+11
\|
*	remove direct dep on event-stream: malisious version was unpublished	Aleksey Kladov	2018-12-09	1	-125/+39
\|
*	Add package command and upgrade event-stream	DJMcNab	2018-12-08	1	-3/+18
\|
*	Run npm update and add private and preview flags	DJMcNab	2018-12-08	1	-714/+776
\| \| \| \| \| \| \| \|	Private stops npm publish working, which would be nonsensical anyway In case it gets added to the vscode extension repository, preview marks it as such Private may also prevent publishing to the vscode extension repository
*	fix npm problems	Aleksey Kladov	2018-11-27	1	-39/+23
\|
*	Update vscode-languageclient package to support RenameOptions	Jeremy A. Kolb	2018-10-19	1	-8/+8
\|
*	Add on-enter handler	Aleksey Kladov	2018-10-09	1	-393/+393
\| \| \| \|	Now, typing doc comments is much more pleasant
*	Add tslint and prettier to ci	Daniel McNab	2018-10-08	1	-370/+580
\|
*	rename all things	Aleksey Kladov	2018-09-16	1	-0/+2419