JSR now lets you diff the generated documentation between released versions of a package, making it easy and clear what has changed in a visual manner!
Example: jsr.io/@david/gagen...
this sounds interesting for @jsr.io
do you see a difference?
old version to a new version selector
changes are coming
We couldn't have built our own docs generation without @deno.land tools, here to collaborate with all registries
@jsr.io 🤝 @npmx.dev
no this is illegal
JSR now has a refreshed & improved browsing and viewing experience for the auto-generated documentation, making it easier than ever before to find what you are looking for!
In just 2 hours another bi-weekly open meeting will occur in our discord.
find out what has recently been worked on, what may come up next, and ask anything you may have questions about!
discord.gg/hMqvhAn9xG
Of course I am there like always
if interested what it actually does, you can take a look at github.com/denoland/den..., all rust code in this directory is what is used for processing the docnodes to make them into the output of generateHTMLasJSON
generateHTMLasJSON (as terribly named as it is), is probably your best bet. it handles references between symbols, grouping of nodes, and many more things (and basically the point of it is handling docnodes edgecases).
yeah raw doc nodes are definitely more flexible, but the amount of edge cases to cover is way more than one might think, still to this day i am fixing edgecases around using raw doc nodes.
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?
jsr.io actually provides this out of the box, with vairous parts being inspired by docs.rs
Bun is fast, until latency matters for Next.js.
We benchmarked the same Next.js app across Node.js, Deno, Bun, and Watt (our multi-threaded Node-based runtime) under identical load on AWS EKS.
Throughput looked fine across the board. Latency told a very different story. 🧵
In his talk at #EuroRust25, @kettmeir.dev shared how the @deno.land project improved error handling by migrating from the anyhow crate to using thiserror and concrete error types – watch it on YouTube now! 🦀
👉 youtu.be/f6eofqicw_s
#RustLang #RustConference #EuroRust
🌕 🌖 🌑
jsr.io
And given that we have the dropdown on docs for various systems, I think that keeping deno.json in documentation is reasonable, and if other config files are compatible with jsr's schema, then they could be added, but ie package.json is not compatible with the schema.
JSR itself doesn't have special handling for deno.json. The only reference of deno.json is in documentation and it being the default value for a database insertion which always has a value set.
we will make him show up, it's just a matter of time!
Leo Kettmeir at RustLab, the International Conference on Rust in Florence, November 9th, 2024 - November 11th 2024
Leo Kettmeir at RustLab, the International Conference on Rust in Florence, November 9th, 2024 - November 11th 2024
Leo Kettmeir at RustLab, the International Conference on Rust in Florence, November 9th, 2024 - November 11th 2024
Diving into the world where Rust meets JavaScript! 🦀 💛
Great insights from Leo Kettmeir on "How to integrate JavaScript in your Rust program" at #RustLab2024. Thank you!
#RustLang
the landing page, if its blank, i assume you have an set entrypoint. in that case, the content of the page are derived from the module doc for the entrypoint file (so a top-level jsdoc comment with a @module tag)
Categories currently are only supported when you are using a single .d.ts file, so its likely to not be of much use to you. However if it does, here is an example: github.com/denoland/doc... is the file we use for docs.deno.com/api/deno
Hey, Leo here from the Deno team; feel free to ask me anything related to it
