| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 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-08-19 | feat(FUTURE): terse lockfile (v4) (#25059) | David Sherret | |
| 2024-05-23 | fix(cli): Support deno.lock with only package.json present + fix DENO_FUTURE ↵ | Nathan Whitaker | |
| install interactions with lockfile (#23918) Fixes #23571. Previously, we required a `deno.json` to be present (or the `--lock` flag) in order for us to resolve a `deno.lock` file. This meant that if you were using deno in an npm-first project deno wouldn't use a lockfile. Additionally, while I was fixing that, I discovered there were a couple bugs keeping the future `install` command from using a lockfile. With this PR, `install` will actually resolve the lockfile (or create one if not present), and update it if it's not up-to-date. This also speeds up `deno install`, as we can use the lockfile to skip work during npm resolution. | |||
 |
index : deno.git | |
| Unnamed repository; edit this file 'description' to name the repository. | User & |
| summaryrefslogtreecommitdiff |