denoland-deno/tests/registry/jsr/@denotest/bad-manifest-checksum/1.0.0_meta.json

{
  "exports": {
    ".": "./mod.ts"
  },
  "manifest": {
    "/mod.ts": {
      "size": 0,
      "checksum": "sha256-bad-checksum"
    }
  }
}
feat(unstable): single checksum per JSR package in the lockfile (#22421) 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. 2024-02-15 14:49:35 -05:00			`{`
			`"exports": {`
			`".": "./mod.ts"`
			`},`
			`"manifest": {`
			`"/mod.ts": {`
			`"size": 0,`
			`"checksum": "sha256-bad-checksum"`
			`}`
			`}`
			`}`