Deno keep panicks on VSCode window with an unsaved new TypeScript file

[kLiHz]

Version: Deno 2.1.4 (stable and canary)

How to reproduce:

• Install Deno
• Install Deno extension in Visual Studio Code (either stable or insider)
• Create a new window in Visual Studio Code
• Create a file (e.g click "New File")
• Set file source type (e.g. click "Select a language") to "TypeScript"
• Got "The Deno Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information."

The output:

Starting Deno language server...
  version: 2.1.4+7cabd02 (release, x86_64-pc-windows-msvc)
  executable: C:\Users\Henry\.deno\bin\deno.EXE
Connected to "Visual Studio Code" 1.96.2
Enabling import suggestions for: https://deno.land
Refreshing configuration tree...

============================================================
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.1.4+7cabd02
Args: ["C:\\Users\\Henry\\.deno\\bin\\deno.EXE", "lsp"]

thread 'main' panicked at C:\a\deno\deno\resolvers\node\package_json.rs:69:41:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[Info  - 1:04:38 PM] Connection to server got closed. Server will restart.

(duaplicated outputs omitted...)

[Error - 1:04:39 PM] The Deno Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
Error retrieving config tasks: Error: Client is not running

Screenshot

I first encountered this bug a while ago, but at that time I couldn't locate its cause. Recently I just accidentally found the way to reproduce it so I'm filing this issue.