8d03397293
- Bundles are fully standalone. They now include the shared loader with `deno_typescript`. - Refactor of the loader in `deno_typescript` to perform module instantiation in a more - Change of behaviour when an output file is not specified on the CLI. Previously a default name was determined and the bundle written to that file, now the bundle will be sent to `stdout`. - Refactors in the TypeScript compiler to be able to support the concept of a request type. This provides a cleaner abstraction and makes it easier to support things like single module transpiles to the userland. - Remove a "dangerous" circular dependency between `os.ts` and `deno.ts`, and define `pid` and `noColor` in a better way. - Don't bind early to `console` in `repl.ts`. - Add an integration test for generating a bundle. |
||
|---|---|---|
| .. | ||
| archive | ||
| bytes | ||
| datetime | ||
| encoding | ||
| examples | ||
| flags | ||
| fmt | ||
| fs | ||
| http | ||
| installer | ||
| io | ||
| log | ||
| media_types | ||
| mime | ||
| multipart | ||
| node | ||
| path | ||
| prettier | ||
| strings | ||
| testing | ||
| textproto | ||
| util | ||
| uuid | ||
| ws | ||
| xeval | ||
| manual.md | ||
| README.md | ||
| style_guide.md | ||
Deno Standard Modules
These modules do not have external dependencies and they are reviewed by the Deno core team. The intention is to have a standard set of high quality code that all Deno projects can use fearlessly.
Contributions are welcome!
How to use
These modules are tagged in accordance with Deno releases. So, for example, the
v0.3.0 tag is guaranteed to work with deno v0.3.0. You can link to v0.3.0 using
the URL https://deno.land/std@v0.3.0/
It's strongly recommended that you link to tagged releases rather than the master branch. The project is still young and we expect disruptive renames in the future.
Documentation
Here are the dedicated documentations of modules:
Contributing
deno_std is a loose port of Go's standard library. When in doubt, simply port Go's source code, documentation, and tests. There are many times when the nature of JavaScript, TypeScript, or Deno itself justifies diverging from Go, but if possible we want to leverage the energy that went into building Go. We generally welcome direct ports of Go's code.
Please ensure the copyright headers cite the code's origin.
Follow the style guide.