1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-12-27 17:49:08 -05:00
denoland-deno/std
Casper Beyer bee36a4de8
test(std/http): make tests runnable from any directory (#7441)
This makes std/http tests runnable from any directory by spawning test
processes in the module directory resolved from import.meta.url and
resolving test data relative to the same module directory.
2020-09-14 12:58:43 +02:00
..
_util feat: update to TypeScript 4.0 (#6514) 2020-08-24 19:43:54 -04:00
archive test(std/archive): make tests runnable from any directory (#7366) 2020-09-06 19:52:53 +02:00
async test(std): ensure mod.ts modules have a test coverage (#7264) 2020-08-31 22:26:55 -04:00
bytes doc(std/bytes): Fix wrong import in the example code (copyBytes) (#6787) 2020-07-18 15:06:42 -04:00
datetime test(std/datetime): port golang dayOfYear tests (#7105) 2020-08-27 11:12:49 +02:00
encoding test(std/encoding): make tests runnable from any directory (#7368) 2020-09-06 19:48:53 +02:00
examples chore(std): remove std/ws connect method (#7403) 2020-09-09 21:33:38 +02:00
flags test(std): ensure mod.ts modules have a test coverage (#7264) 2020-08-31 22:26:55 -04:00
fmt chore: remove unreachable code to pass linter (#7270) 2020-08-31 11:10:28 +02:00
fs test(std/fs): make tests runnable from any directory (#7388) 2020-09-08 11:43:43 +02:00
hash test(std/hash): make tests runnable from any directory (#7376) 2020-09-07 11:32:24 +02:00
http test(std/http): make tests runnable from any directory (#7441) 2020-09-14 12:58:43 +02:00
io test(std): ensure mod.ts modules have a test coverage (#7264) 2020-08-31 22:26:55 -04:00
log docs(std/log): update example (#7157) 2020-08-27 11:03:49 +02:00
mime test(std/mime): make tests runnable from any directory (#7398) 2020-09-09 11:24:47 +02:00
node upgrade: deno_doc, deno_lint, dprint, swc (#7434) 2020-09-13 14:15:38 +02:00
path test(std): ensure mod.ts modules have a test coverage (#7264) 2020-08-31 22:26:55 -04:00
permissions Use dprint for internal formatting (#6682) 2020-07-14 15:24:17 -04:00
signal Use dprint for internal formatting (#6682) 2020-07-14 15:24:17 -04:00
testing fix(std/testing): invalid dates assertion equality (#7230) 2020-08-28 19:59:28 -04:00
textproto Use dprint for internal formatting (#6682) 2020-07-14 15:24:17 -04:00
uuid docs(std/uuid): remove mention of v3 which is not supported (#7318) 2020-09-01 19:18:40 -04:00
wasi test(std/wasi): explicitly list modules for deterministic test runs (#7245) 2020-09-04 07:14:51 -04:00
ws chore(std): remove std/ws connect method (#7403) 2020-09-09 21:33:38 +02:00
README.md chore(std): edit style guide link to deno manual (#6490) 2020-07-14 14:54:13 +02:00
tsconfig_test.json feat(unstable): enable importsNotUsedAsValues by default (#7413) 2020-09-11 16:22:10 +02:00
version.ts v1.4.0 2020-09-13 16:35:31 +02:00

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 will eventually be tagged in accordance with Deno releases but as of today we do not yet consider them stable and so we version the standard modules differently from the Deno runtime to reflect this.

It is strongly recommended that you link to tagged releases to avoid unintended updates and breaking changes.

Don't link to / import any module whose path:

  • Has a name or parent with an underscore prefix: _foo.ts, _util/bar.ts.
  • Is that of a test module or test data: test.ts, foo_test.ts, testdata/bar.txt.

Don't import any symbol with an underscore prefix: export function _baz() {}.

These elements are not considered part of the public API, thus no stability is guaranteed for them.

Documentation

To browse documentation for 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.