docs(embedding_deno): added an overview of all deno crates and what they do. #471
Conversation
|
|
There was a problem hiding this comment.
These crates are documented in the READMEs in their own repos/dirs. Do we want to duplicate those docs in this format? cc @ry @piscisaureus @bartlomieju
A list of all deno related crates are also available in https://crates.io/teams/github:denoland:engineering
I'd argue that it's better to document it in the manual for easier access. No one wants to scavange for this kind of information. |
I think it's fine to document them here too |
| ### [`deno`](https://crates.io/crates/deno) | ||
|
|
||
| The real deal. | ||
|
|
||
| has All the user facing features of deno including typescript compilation and | ||
| dependancy managment in a binary package. |
There was a problem hiding this comment.
it should be mentioned that this isnt published as a library anymore
| additional rust based deno operators. | ||
|
|
||
| It does not implement anything either than that and you have to register | ||
| external deno operators to do anything useful. |
There was a problem hiding this comment.
operators
what are operators?
| - Text Encoding | ||
| - Text Decoding | ||
| - [File Standard](https://w3c.github.io/FileAPI/) | ||
|
|
There was a problem hiding this comment.
streams, compression streams, performance, abortsignal, timers, messagechannel, base64
|
there are other crates as well, like v8 & urlpattern, and probably a bunch more i am forgetting |
Closes denoland/deno-docs#109
Adds a new chapter that clarifies what deno crates do and links to them.
Makes it easier to figure out where to even begin constructing your ideal version of Deno.