foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-12-27 17:49:08 -05:00
Code Issues Packages 1 Wiki Activity
denoland-deno/tests/specs/install/future_install_local_deno/deno.lock.out

35 lines
864 B
Text
Raw Normal View History

fix(cli): Support deno.lock with only package.json present + fix DENO_FUTURE 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.
2024-05-23 15:31:05 -04:00
{
feat(FUTURE): terse lockfile (v4) (#25059)
2024-08-18 23:01:39 -04:00
"version": "4",
"specifiers": {
"jsr:@denotest/add": "jsr:@denotest/add@1.0.0",
fix(add): Handle packages without root exports (#25102) Fixes #24607. This PR makes the logic that caches top level dependencies (things present in import map) smarter, so we handle JSR dependencies without root exports.
2024-08-21 18:23:32 -04:00
"jsr:@std/testing": "jsr:@std/testing@1.0.0",
feat(FUTURE): terse lockfile (v4) (#25059)
2024-08-18 23:01:39 -04:00
"npm:@denotest/esm-basic@^1.0.0": "npm:@denotest/esm-basic@1.0.0"
},
"jsr": {
"@denotest/add@1.0.0": {
"integrity": "[WILDCARD]"
fix(add): Handle packages without root exports (#25102) Fixes #24607. This PR makes the logic that caches top level dependencies (things present in import map) smarter, so we handle JSR dependencies without root exports.
2024-08-21 18:23:32 -04:00
},
"@std/testing@1.0.0": {
"integrity": "[WILDCARD]"
feat(FUTURE): terse lockfile (v4) (#25059)
2024-08-18 23:01:39 -04:00
}
},
"npm": {
"@denotest/esm-basic@1.0.0": {
"integrity": "[WILDCARD]"
fix(cli): Support deno.lock with only package.json present + fix DENO_FUTURE 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.
2024-05-23 15:31:05 -04:00
}
},
fix(add): Handle packages without root exports (#25102) Fixes #24607. This PR makes the logic that caches top level dependencies (things present in import map) smarter, so we handle JSR dependencies without root exports.
2024-08-21 18:23:32 -04:00
"remote": {
"http://localhost:4545/subdir/mod1.ts": "[WILDCARD]",
"http://localhost:4545/subdir/print_hello.ts": "[WILDCARD]",
"http://localhost:4545/subdir/subdir2/mod2.ts": "[WILDCARD]",
"http://localhost:4545/v1/extensionless": "[WILDCARD]"
},
fix(cli): Support deno.lock with only package.json present + fix DENO_FUTURE 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.
2024-05-23 15:31:05 -04:00
"workspace": {
"dependencies": [
"jsr:@denotest/add",
fix(add): Handle packages without root exports (#25102) Fixes #24607. This PR makes the logic that caches top level dependencies (things present in import map) smarter, so we handle JSR dependencies without root exports.
2024-08-21 18:23:32 -04:00
"jsr:@std/testing",
fix(cli): Support deno.lock with only package.json present + fix DENO_FUTURE 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.
2024-05-23 15:31:05 -04:00
"npm:@denotest/esm-basic@^1.0.0"
]
}
}
Copy permalink