500b97dde6
For some reason, the unit tests for Deno.remove() were not being imported to unit_tests.ts and, consequently, not being executed. Thus, I imported them, refactored some existent ones and wrote new ones for the symlink removal case. Since the creation of a symlink is not implemented for Windows yet, assertions that consider this state were added when the tests are executed in this OS. |
||
|---|---|---|
| .ci | ||
| archive | ||
| bytes | ||
| datetime | ||
| encoding | ||
| examples | ||
| flags | ||
| fmt | ||
| fs | ||
| http | ||
| io | ||
| log | ||
| media_types | ||
| mime | ||
| node | ||
| path | ||
| strings | ||
| testing | ||
| textproto | ||
| util | ||
| uuid | ||
| ws | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.json | ||
| .gitignore | ||
| azure-pipelines.yml | ||
| format.ts | ||
| LICENSE | ||
| manual.md | ||
| README.md | ||
| style_guide.md | ||
NOTICE: The deno_std repository has been moved to the main Deno repo
https://github.com/denoland/deno/tree/master/std
All PRs and issues should be directed to denoland/deno, not here.
We are in a transitional phase now as we update various references to this repository. Eventually this repo will be archived.
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.