Closed mskian closed 1 year ago
I had similar issues updating NPM packages. I think it's because Deno caches the npm package internally.
You can remove the Deno cache directory (deno info
) or run the Lume task with the --reload
flag:
{
"importMap": "./import_map.json",
"tasks": {
"lume": "echo \"import 'lume/cli.ts'\" | deno run --reload --unstable -A -",
"build": "deno task lume",
"serve": "deno task lume -s"
}
}
Once you run it with --reload
, you can remove the flag because the new package is cached.
Probably it's caused by the deno.lock file? Related: https://github.com/denoland/deno/issues/16721
I had similar issues updating NPM packages. I think it's because Deno caches the npm package internally. You can remove the Deno cache directory (
deno info
) or run the Lume task with the--reload
flag:{ "importMap": "./import_map.json", "tasks": { "lume": "echo \"import 'lume/cli.ts'\" | deno run --reload --unstable -A -", "build": "deno task lume", "serve": "deno task lume -s" } }
Once you run it with
--reload
, you can remove the flag because the new package is cached.
Fixed...
yes because of deno.lock
file
deno 1.28
Generate a Lock File Now
Probably lume upgrade
should remove the deno.lock
file.
Version
1.13.2
Platform
Ubuntu 20.04
What steps will reproduce the bug?
Build error
How often does it reproduce? Is there a required condition?
What is the expected behavior?
Build Error
What do you see instead?
No issues in
1.31.1