deno.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2024-09-14	feat: TypeScript 5.6 and `npm:@types/node@22` (#25614)	David Sherret

2024-08-28	feat: improve lockfile v4 to store normalized version constraints and be ↵	David Sherret
	more terse (#25247) Stores normalized version constraints in the lockfile, which will improve reproducibility and will fix a bug with duplicate specifiers ending up in the lockfile. Also, gets rid of some duplicate data in the specifiers area of the lockfile.
2024-06-28	refactor(cli): Create wrapper around `deno_lockfile::Lockfile` (#24366)	Nathan Whitaker
	As suggested in https://github.com/denoland/deno/pull/24355#discussion_r1657875422. I wasn't able to hide the mutex stuff as much as I'd like (ended up just adding an escape hatch `inner()` method that locks the inner mutex), because you can't return references to the inner fields through a mutex. This is mostly motivated by the frozen lockfile changes
2024-06-11	fix(npm): resolve dynamic npm imports individually (#24170)	David Sherret
	* https://github.com/denoland/deno_npm/pull/57 * https://github.com/denoland/deno_graph/pull/498 Closes https://github.com/denoland/deno/issues/17802
2024-06-05	refactor(npm): improve locking around updating npm resolution (#24104)	David Sherret
	Introduces a `SyncReadAsyncWriteLock` to make it harder to write to the npm resolution without first waiting async in a queue. For the npm resolution, reading synchronously is fine, but when updating, someone should wait async, clone the data, then write the data at the end back.
2024-06-05	fix: better handling of npm resolution occurring on workers (#24094)	David Sherret
	Closes https://github.com/denoland/deno/issues/24063
2024-05-28	feat(vendor): support modifying remote files in vendor folder without ↵	David Sherret
	checksum errors (#23979) Includes: * https://github.com/denoland/deno_graph/pull/486 * https://github.com/denoland/deno_graph/pull/488 * https://github.com/denoland/deno_lockfile/pull/25 * https://github.com/denoland/deno_lockfile/pull/22 * https://github.com/denoland/deno_graph/pull/483 * https://github.com/denoland/deno_graph/pull/470
2024-04-05	perf(lsp): use lockfile to reduce npm pkg resolution time (#23247)	David Sherret
	This functionality was broken. The series of events was: 1. Load the npm resolution from the lockfile. 2. Discover only a subset of the specifiers in the documents. 3. Clear the npm snapshot. 4. Redo npm resolution with the new specifiers (~500ms). What this now does: 1. Load the npm resolution from the lockfile. 2. Discover only a subset of the specifiers in the documents and take into account the specifiers from the lockfile. 3. Do not redo resolution (~1ms).
2024-01-22	feat(lockfile): track JSR and npm dependencies in config file (#22004)	David Sherret
	See overview in https://github.com/denoland/deno_lockfile/pull/13
2024-01-01	chore: update copyright to 2024 (#21753)	David Sherret

2023-10-02	refactor(npm): make `NpmCache`, `CliNpmRegistryApi`, and `NpmResolution` ↵	David Sherret
	internal to `npm::managed` (#20764)
2023-09-30	refactor(npm): create `cli::npm::managed` module (#20740)	David Sherret
	Creates the `cli::npm::managed` module and starts moving more functionality into it.