Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.
Platform: windows x86_64
Version: 2.6.3
Args: ["\\\\?\\C:\\Users\\ganuo\\.deno\\bin\\deno.EXE", "run", "-P=lume", "lume/cli.ts", "-s"]
View stack trace at:
https://panic.deno.com/v2.6.3/x86_64-pc-windows-msvc/yy-sI-5nwtCyh9xtC-28xtC818xtCij8luE857luE0r7luEi4mo0B63l5NgymRyt16Tglu2jB-silkB4oglkBnn_rkgD9_lz8_Drv9g7_D7sqm9_D_-wj8_Dt467jgD3kqhigDvvqgkgDrwktkgD0m-k5Cqokl5Ckoll5Cqopv-Cinov-C28qpdl0-rkgDhlz67_Dp-jtkgDromtkgD-p-k5Cmq6k5Cmmx82Cw9x82Cqgpz2Ckwlwdytsvd2m_61Bwvw51Bs_o41Bklg31Bymw14B4po1tCut0L4zijB
thread 'worker-1' (20152) panicked at C:\Users\runneradmin\.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\deno_path_util-0.6.4\src\lib.rs:267:66:
range end index 70 out of range for slice of length 55
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace