aboutsummaryrefslogtreecommitdiff
path: root/editors/code/package-lock.json
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* Add package command and upgrade event-streamDJMcNab2018-12-081-3/+18
|
* Run npm update and add private and preview flagsDJMcNab2018-12-081-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 problemsAleksey Kladov2018-11-271-39/+23
|
* Update vscode-languageclient package to support RenameOptionsJeremy A. Kolb2018-10-191-8/+8
|
* Add on-enter handlerAleksey Kladov2018-10-091-393/+393
| | | | Now, typing doc comments is much more pleasant
* Add tslint and prettier to ciDaniel McNab2018-10-081-370/+580
|
* rename all thingsAleksey Kladov2018-09-161-0/+2419
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 12:39:52 +0000