mirror of
https://github.com/denoland/deno.git
synced 2024-12-22 07:14:47 -05:00
4f80d83774
This changes the lockfile to not store JSR specifiers in the "remote"
section. Instead a single JSR integrity is stored per package in the
lockfile, which is a hash of the version's `x.x.x_meta.json` file, which
contains hashes for every file in the package. The hashes in this file
are then compared against when loading.
Additionally, when using `{ "vendor": true }` in a deno.json, the files
can be modified without causing lockfile errors—the checksum is only
checked when copying into the vendor folder and not afterwards
(eventually we should add this behaviour for non-jsr specifiers as
well). As part of this change, the `vendor` folder creation is not
always automatic in the LSP and running an explicit cache command is
necessary. The code required to track checksums in the LSP would have
been too complex for this PR, so that all goes through deno_graph now.
The vendoring is still automatic when running from the CLI.
|
||
|---|---|---|
| .. | ||
| testing | ||
| analysis.rs | ||
| cache.rs | ||
| capabilities.rs | ||
| client.rs | ||
| code_lens.rs | ||
| completions.rs | ||
| config.rs | ||
| diagnostics.rs | ||
| documents.rs | ||
| jsr_resolver.rs | ||
| language_server.rs | ||
| logging.rs | ||
| lsp_custom.rs | ||
| mod.rs | ||
| npm.rs | ||
| parent_process_checker.rs | ||
| path_to_regex.rs | ||
| performance.rs | ||
| README.md | ||
| refactor.rs | ||
| registries.rs | ||
| repl.rs | ||
| semantic_tokens.rs | ||
| text.rs | ||
| tsc.rs | ||
| urls.rs | ||
Deno Language Server
The Deno Language Server provides a server implementation of the
Language Server Protocol
which is specifically tailored to provide a Deno view of code. It is
integrated into the command line and can be started via the lsp sub-command.
This documentation has been moved to the Deno manual.