mirror of
https://github.com/denoland/deno.git
synced 2024-11-27 16:10:57 -05:00
5de30c5323
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.
22 lines
460 B
Text
22 lines
460 B
Text
{
|
|
"version": "3",
|
|
"packages": {
|
|
"specifiers": {
|
|
"jsr:@denotest/add": "jsr:@denotest/add@1.0.0",
|
|
"npm:@denotest/esm-basic@^1.0.0": "npm:@denotest/esm-basic@1.0.0"
|
|
},
|
|
"jsr": {
|
|
"@denotest/add@1.0.0": [WILDCARD]
|
|
},
|
|
"npm": {
|
|
"@denotest/esm-basic@1.0.0": [WILDCARD]
|
|
}
|
|
},
|
|
"remote": [WILDCARD],
|
|
"workspace": {
|
|
"dependencies": [
|
|
"jsr:@denotest/add",
|
|
"npm:@denotest/esm-basic@^1.0.0"
|
|
]
|
|
}
|
|
}
|