Post

is it a choice to not render jsdoc `@example`s or is it just a library limitation? based on the generated docs for my little package `binary-util`

js doc `@examples` were working for other packages that I was checking, but likely I missed something! tons of edge cases here--mind if I poke around later?

I wouldn't be surprised if I'm just misusing it tbh... 😖

cc @donmccurdy.com

sorry if i'm being dense, but is this a PR on the Svelte repo? 👀

nope, it's something we're working on - a better npmjs​.com! will dm you more

Thank you!! Lots of fun directions we can take this, and I'm sure I missed some edge cases. Real heavy lifting here and shoutout goes to the @deno.land folks for providing the underlying tooling. All I did was a little glue code really.

great to see deno_doc being used! how are you using it exactly? are you using the actual html renderer and modifying the output, `generateHtmlAsJSON`, or raw doc nodes?

pretty naively in this first pass! i'm basically: 1. fetching type urls from esh.sh with an `x-typescript-types` header 2. run it `@deno/doc` slightly patched to get WASM to work on a vercel function 3. take the `DenoDocNode[]` structured AST result 4. flatten, transform, merge, render to HTML

woah -- where can I see this? (link?)

slick! though i think i just discovered something about typescript, namely that non-exported declarations are still externally visible? e.g. `Primitive` isn't exported from the `$state` namespace, it's supposed to be a private implementation detail. hmm...

one fun thing i learned from this little deep dive into `deno docs`' output is that it gets a ton of info that I wouldn't have expected so might be other things exposed here that we didn't expect to show up!

possibly! would be curious to take a look, if it's online somewhere or easy to spin up locally?

it might be our mistake!

it's not, it's our bad — opened a PR github.com/sveltejs/sve...