Our thinking is that when people think of Deno and TypeScript, they think about them in the context of JavaScript.
​
It's helpful for our authors for us to have "JavaScript ecosystem" categories underneath JavaScript, not just JavaScript frameworks.
​
This way, they also show up in the JavaScript parent category as well (which is helpful), which they would not otherwise unless the author also added the JavaScript category.
​
So, this is why we put certain runtimes and languages under the JavaScript category, and why the Deno category and the TypeScript category are underneath JavaScript...