Deno doc breaks on a deno.json problem

[iherman]

Here is the full output of deno with the full trace environment option on:

15:36 yml2vocab-d> RUST_BACKTRACE=full deno doc --html index.ts
Warning "exports" field should be specified when specifying a "name".
    at file:///Users/ivan/W3C/github/VC/yml2vocab-d/deno.json

============================================================
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: macos aarch64
Version: 2.0.0
Args: ["deno", "doc", "--html", "index.ts"]

thread 'main' panicked at /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/deno_doc-0.152.0/src/html/symbols/namespace.rs:131:47:
called `Option::unwrap()` on a `None` value
stack backtrace:
   0:        0x1022e35a0 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h41035ce174e31160
   1:        0x1013ff464 - core::fmt::write::h7e946826fce7616b
   2:        0x1022b4450 - std::io::Write::write_fmt::he3645adfefb23e4a
   3:        0x1022e5f60 - std::sys_common::backtrace::print::h2efe9ae66fda73dc
   4:        0x1022e5878 - std::panicking::default_hook::{{closure}}::hd27200b4fbd3bf40
   5:        0x1022e5480 - std::panicking::default_hook::hb8656334461229c8
   6:        0x1013123d4 - deno::setup_panic_hook::{{closure}}::h7147d95f405b9523
   7:        0x1022e6850 - std::panicking::rust_panic_with_hook::h10171cf76e1aed15
   8:        0x1022e62a8 - std::panicking::begin_panic_handler::{{closure}}::h9344de43a47cae21
   9:        0x1022e623c - std::sys_common::backtrace::__rust_end_short_backtrace::h55013ada3ab9c4e8
  10:        0x1022e6230 - _rust_begin_unwind
  11:        0x1013fd938 - core::panicking::panic_fmt::h0b16bb09366e1f01
  12:        0x1013ff178 - core::panicking::panic::h61ea408fdd25f03d
  13:        0x101405d2c - core::option::unwrap_failed::h3e439429fd11306f
  14:        0x101634248 - <core::iter::adapters::filter_map::FilterMap<I,F> as core::iter::traits::iterator::Iterator>::next::h6e0272c708ea64ab
  15:        0x101632c90 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once::h404b8479ded4d66a
  16:        0x101635b34 - <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::next::h9c11255a5e355bd7
  17:        0x10165997c - deno_doc::html::generate::hd38997749d303250
  18:        0x10127c870 - deno::tools::doc::doc::{{closure}}::h83fcd094f08b2620
  19:        0x10130d7e8 - deno::spawn_subcommand::{{closure}}::hf15f4c997da1b3e0
  20:        0x100f38374 - <deno_unsync::tokio::task::MaskFutureAsSend<F> as core::future::future::Future>::poll::ha64be5ed1c07a63e
  21:        0x10109fd28 - tokio::runtime::task::raw::poll::h785f0ebc6e8fb51d
  22:        0x101313970 - deno::main::h398892cededa77b5
  23:        0x100fda5cc - std::sys_common::backtrace::__rust_begin_short_backtrace::h8f1581c35b9b24a1
  24:        0x10137b650 - _main

[bartlomieju]

This problem was already fixed in #26100 and will be released in Deno 2.0.1 later today. You can upgrade do canary version in the meantime to workaround it (deno upgrade canary)