deno.lock conflict, dispite no visible deno.lock file

I swear I don't have aa deno.lock file. Even attempting to run

deno clean
deno check https://esm.sh/@msgpack/msgpack@2.8.0

deno clean
deno check https://esm.sh/@msgpack/msgpack@2.8.0

I'm still getting the following error:

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/@msgpack/msgpack@2.8.0
  Actual: db17860b46cb00bea7e13527dc49a1ae774e5155bc087d4173adbbb77808b123
  Expected: 5d2970104ab58ae3097b031bb27ec285694dabc1032a316f945379137b5645ea

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.

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/@msgpack/msgpack@2.8.0
  Actual: db17860b46cb00bea7e13527dc49a1ae774e5155bc087d4173adbbb77808b123
  Expected: 5d2970104ab58ae3097b031bb27ec285694dabc1032a316f945379137b5645ea

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.

Which would be fine if I could find & delete the lockfile. But I don't know where the lockfile is or how to find it (on ubuntu linux via command line).

Can someone please help me? I was in the middle of debugging a project when I ran head-first into this wall.

deno.lock conflict, dispite no visible deno.lock file

I swear I don't have aa deno.lock file. Even attempting to run

deno clean
deno check https://esm.sh/@msgpack/msgpack@2.8.0

deno clean
deno check https://esm.sh/@msgpack/msgpack@2.8.0

I'm still getting the following error:

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/@msgpack/msgpack@2.8.0
  Actual: db17860b46cb00bea7e13527dc49a1ae774e5155bc087d4173adbbb77808b123
  Expected: 5d2970104ab58ae3097b031bb27ec285694dabc1032a316f945379137b5645ea

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.

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/@msgpack/msgpack@2.8.0
  Actual: db17860b46cb00bea7e13527dc49a1ae774e5155bc087d4173adbbb77808b123
  Expected: 5d2970104ab58ae3097b031bb27ec285694dabc1032a316f945379137b5645ea

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.

deno.lock conflict, dispite no visible deno.lock file

deno.lock conflict, dispite no visible deno.lock file

Continue the conversation

Deno

Continue the conversation

Deno

Similar Threads