48dd1d7053
⬆️ npm deps
2020-02-17 11:13:16 +01:00
2225cadd5a
update lockfile
2020-02-17 11:12:45 +01:00
de3b0b43f3
Expect vscode 1.42
2020-02-14 12:02:19 -05:00
bd3a41cc33
Prevent auto-update of dev extension
2020-02-14 15:29:19 +01:00
a63659badb
vscode: replaced unwrapNotNil() with ! as per @matklad
2020-02-09 13:59:27 +02:00
5d88c1db38
vscode: amended config to use binary from globalStoragePath, added ui for downloading
2020-02-08 04:34:11 +02:00
3e0e4e90ae
added fetchLatestArtifactMetadata() and downloadFile() functions
2020-02-08 04:34:11 +02:00
9b8e3b80ee
Remove rollup-typescript
...
It seems like just calling typescript directly is simpler and more reliable?
2020-02-03 17:39:34 +01:00
0a68dfb491
Update some rollup packages
2020-02-03 16:49:25 +01:00
ad57726f91
Use simple prng instead of a dependency
...
closes #2999
2020-02-03 16:37:12 +01:00
30f7e6590a
Remove recent improvements to the build script
...
tslib as a dev dependency and commonjs modules are definitely *wrong*
in the ideal world, **but** in the real world that's the only
combination that works. See
https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/Problems.20with.20TypeScript.20build
2020-02-03 15:25:29 +01:00
0ade5cb2b3
vscode: dropped npm-check-updates script
2020-02-03 00:05:49 +02:00
e9800b0023
vscode: updated rollup typescript so it typechecks the bundle
2020-02-03 00:05:49 +02:00
f08297983f
vscode: moved tslib to runtime dependencies and added \"importHelpers\": true
2020-02-01 23:11:39 +02:00
c378133185
⬆️ node
2020-01-28 15:11:44 +01:00
1266810e55
vscode-languageclient 6.1.0
...
Adds support for proposed semantic highlighting extension
2020-01-27 10:25:22 -05:00
a0494c7237
vscode-languageclient 6.0.1
2020-01-20 19:48:32 -05:00
385c548032
Language Server Protocol 3.15 is now stable
...
Update the client
2020-01-14 14:53:38 -05:00
a39fe4f1dc
vscode-languageclient 6.0.0-next.10
2020-01-13 16:49:44 -05:00
bd7aa5db14
Rename VS Code extension to rust-analyzer
2020-01-13 11:13:18 +01:00
ff0ceb30a9
Add semicolons
2019-12-31 18:55:34 +01:00
323ad13c8a
Add tsfmt
2019-12-30 23:28:13 +01:00
9fae4f4b99
Remove prettier
2019-12-30 23:27:13 +01:00
a0c0350960
Add prettier
2019-12-30 15:10:59 +01:00
e0fa096bbb
Add rollup
2019-12-30 11:20:45 +01:00
5846221a39
Minimize TypeScript build
2019-12-30 02:22:52 +01:00
25537d294c
Fix https://github.com/rust-analyzer/rust-analyzer/pull/2061#discussion_r348716036
...
Fix https://github.com/rust-analyzer/rust-analyzer/pull/2061/files/68a5ff050faf514e9d122212a66703ca8ce66ab7#r361019340
2019-12-24 00:04:36 +01:00
be78e3c224
Update to latest packages
2019-12-20 13:52:11 -05:00
da29b7fb14
use pretter settings in ts-lint
2019-12-17 23:50:18 +08:00
81ce9833a5
Add rollup sourcemap and fix launch.json
2019-12-09 03:58:43 +08:00
c7dc067104
Code: bump deps
2019-12-08 20:39:22 +02:00
78e8934976
Code: check whether the LSP binary is in PATH
2019-12-08 15:04:37 +02:00
ab7469240c
Fix npm vulnerability warning
2019-12-06 11:41:51 +08:00
de32ae75f8
Bump rollup and vsce
2019-10-10 10:19:05 -04:00
2151d4da6a
add rollup bundler for vscode extension
2019-09-23 23:25:16 +02:00
b58f84626f
Switch to @types/vscode and vscode-test
...
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.
2019-08-26 08:22:48 +02:00
c1dcdd4735
⬆️ npm
2019-07-29 11:22:56 +03:00
38f3b47a00
⬆️ npm deps
2019-07-25 12:17:27 +03:00
83ab841bfa
Bump lodash from 4.17.11 to 4.17.14 in /editors/code
...
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] <support@github.com >
2019-07-11 23:44:16 +00:00
45d6f47c28
Update vsce to latest
2019-07-03 09:55:48 -04:00
5bf3e949e8
Semantic highlighting spike
...
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?
2019-05-27 11:26:33 +02:00
bf7cdec9dd
⬆️ code
2019-04-21 11:32:48 +03:00
b84d0fc1a3
Add proper process teminate method
2019-04-02 15:03:31 +08:00
48d6a52ac1
Update dependencies
2019-02-10 10:32:45 +00:00
9138317021
Add support for a seperate output channel for trace messages
2019-02-10 10:06:33 +00:00
2c7a07e4e8
Update npm packages
2019-02-07 14:55:09 -05:00
b5466f3fb3
Address issues flagged in review
2019-01-19 15:37:26 +03:00
afaa26636e
Add additional pattern variants
2019-01-19 15:37:25 +03:00
7642cf5fe7
⬆️ npm
2019-01-13 21:43:13 +03:00
d61707b4e1
index stuff produced by macros
2019-01-03 21:29:17 +03:00
Aleksey Kladov