aboutsummaryrefslogtreecommitdiff
path: root/editors/code/package-lock.json
Commit message (Collapse)AuthorAgeFilesLines
* Prevent auto-update of dev extensionAleksey Kladov2020-02-141-1/+1
|
* vscode: replaced unwrapNotNil() with ! as per @matkladVeetaha2020-02-091-13/+0
|
* vscode: amended config to use binary from globalStoragePath, added ui for ↵Veetaha2020-02-081-0/+13
| | | | downloading
* added fetchLatestArtifactMetadata() and downloadFile() functionsVeetaha2020-02-081-0/+25
|
* Remove rollup-typescriptAleksey Kladov2020-02-031-10/+0
| | | | It seems like just calling typescript directly is simpler and more reliable?
* Update some rollup packagesAleksey Kladov2020-02-031-26/+29
|
* Use simple prng instead of a dependencyAleksey Kladov2020-02-031-11/+0
| | | | closes #2999
* Remove recent improvements to the build scriptAleksey Kladov2020-02-031-7/+8
| | | | | | | | 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
* vscode: dropped npm-check-updates scriptVeetaha2020-02-021-2010/+0
|
* vscode: updated rollup typescript so it typechecks the bundleVeetaha2020-02-021-5/+2015
|
* vscode: moved tslib to runtime dependencies and added \"importHelpers\": trueVeetaha2020-02-011-2/+1
|
* :arrow_up: nodeAleksey Kladov2020-01-281-41/+41
|
* vscode-languageclient 6.1.0kjeremy2020-01-271-12/+12
| | | | Adds support for proposed semantic highlighting extension
* vscode-languageclient 6.0.1Jeremy Kolb2020-01-211-11/+11
|
* Language Server Protocol 3.15 is now stablekjeremy2020-01-141-15/+15
| | | | Update the client
* vscode-languageclient 6.0.0-next.10kjeremy2020-01-131-15/+15
|
* Rename VS Code extension to rust-analyzerAleksey Kladov2020-01-131-2/+2
|
* Add semicolonsAleksey Kladov2019-12-311-0/+113
|
* Add tsfmtAleksey Kladov2019-12-301-0/+64
|
* Remove prettierAleksey Kladov2019-12-301-6/+0
|
* Add prettierAleksey Kladov2019-12-301-0/+6
|
* Add rollupAleksey Kladov2019-12-301-17/+709
|
* Minimize TypeScript buildAleksey Kladov2019-12-301-1675/+0
|
* Fix ↵Seivan Heidari2019-12-231-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 packageskjeremy2019-12-201-25/+25
|
* use pretter settings in ts-lintEdwin Cheng2019-12-171-0/+39
|
* Add rollup sourcemap and fix launch.jsonEdwin Cheng2019-12-081-0/+53
|
* Code: bump depsLaurențiu Nicola2019-12-081-399/+232
|
* Code: check whether the LSP binary is in PATHLaurențiu Nicola2019-12-081-0/+5
|
* Fix npm vulnerability warningEdwin Cheng2019-12-061-3/+3
|
* Bump rollup and vscekjeremy2019-10-101-27/+19
|
* add rollup bundler for vscode extensionJasperDeSutter2019-09-231-15/+175
|
* Switch to `@types/vscode` and `vscode-test`Bastian Köcher2019-08-261-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: npmAleksey Kladov2019-07-291-104/+93
|
* :arrow_up: npm depsAleksey Kladov2019-07-251-9/+9
|
* Bump lodash from 4.17.11 to 4.17.14 in /editors/codedependabot[bot]2019-07-121-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 latestkjeremy2019-07-031-40/+41
|
* Semantic highlighting spikePascal Hertleif2019-05-271-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: codeAleksey Kladov2019-04-211-1432/+175
|
* Add proper process teminate methodEdwin Cheng2019-04-021-0/+51
|
* Update dependenciesDJMcNab2019-02-101-6/+6
|
* Add support for a seperate output channel for trace messagesDJMcNab2019-02-101-7/+7
|
* Update npm packageskjeremy2019-02-071-92/+58
|
* Address issues flagged in reviewMarcus Klaas de Vries2019-01-191-45/+45
|
* Add additional pattern variantsMarcus Klaas de Vries2019-01-191-45/+45
|
* :arrow_up: npmAleksey Kladov2019-01-131-66/+66
|
* index stuff produced by macrosAleksey Kladov2019-01-031-436/+436
|
* Reload package-lock.jsonDJMcNab2018-12-191-72/+78
|
* use new clear-terminal featureAleksey Kladov2018-12-151-11/+11
|
* remove direct dep on event-stream: malisious version was unpublishedAleksey Kladov2018-12-091-125/+39
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-20 08:38:41 +0000