8000 deno.lock and checksum issue · Issue #326 · Starcounter-Jack/JSON-Patch · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
deno.lock and checksum issue #326
Open
@Amatewasu

Description

@Amatewasu

I include fast-json-patch to my TypeScript deno with the following manner:

import {
  compare,
  getValueByPointer,
  Operation,
} from "https://esm.sh/fast-json-patch@3.1.1";

By doing that, the following lines are added to my deno.lock file:

  "remote": {
    "https://esm.sh/fast-json-patch@3.1.1": "af46ff8943971c21b2722f5d715096f5b8eacea5174c463c2635d6d4e40351db"
  },

However, it makes the sha1 checksum fails when checking the project (using typescript and deno check):

$ deno task check
Task check deno check **/*.ts
Download https://esm.sh/fast-json-patch@3.1.1
error: Integrity check failed for remote specifier. The source code is invalid, as it does not match the expected hash in the lock file.
  Specifier: https://esm.sh/fast-json-patch@3.1.1
  Actual: 3ba5e3a9aebdadb2433526dd7b1d771b4ae25f7d3000bc320ca00e5b91d37284
  Expected: af46ff8943971c21b2722f5d715096f5b8eacea5174c463c2635d6d4e40351db
This could be caused by:
  * the lock file may be corrupt
  * the source itself may be corrupt
Investigate the lockfile; delete it to regenerate the lockfile or --reload to reload the source code from the server.

My current workaround is to remove the remote part of the deno.lock file when it is added automatically.

How could we fix this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0