summaryrefslogtreecommitdiff
path: root/cli/tests/testdata
AgeCommit message (Collapse)Author
2022-06-07refactor(core): Move Deno.core bindings to ops (#14793)Nayeem Rahman
2022-06-06fix: Format non-error exceptions (#14604)Nayeem Rahman
This commit adds "Deno.core.setFormatExceptionCallback" which can be used to provide custom formatting for errors. It is useful in cases when user throws something that is non-Error (eg. a string, plain object, etc).
2022-06-02chore: fix flaky `integration::bench::multifile_summary` test (#14771)Geert-Jan Zwiers
2022-06-01feat: update to TypeScript 4.7 (#14242)Kitson Kelly
2022-05-23fix: read raw stdin to prevent buffering (regression) (#14704)David Sherret
2022-05-23fix: deno task should actually use current exe for `deno` command (#14705)David Sherret
2022-05-22fix(coverage): do not report transpiled files with no lines (#14699)Colin Ihrig
This commit omits files from the coverage report that have no lines of code to report coverage for. Fixes: https://github.com/denoland/deno/issues/14683
2022-05-20refactor: upgrade to deno_ast 0.15 (#14680)David Sherret
2022-05-20fix: prevent Deno.exit to fail when dispatchEvent tampered (#14665)Yoshiya Hinosawa
Co-authored-by: Colin Ihrig <cjihrig@gmail.com>
2022-05-19fix(bench): update typo in bench summary (#14672)Geert-Jan Zwiers
2022-05-18refactor: use spawn API across codebase (#14414)Leo Kettmeir
2022-05-18fix(ext/tls): ability to ignore IP-address certificate errors (#14610)Aleksei Kosyrev
2022-05-17feat: subcommands type-check only local files by default (#14623)Bartek Iwańczuk
This commit changes default mode of type-checking to "local" and adds "--check" flag to following subcommands: - deno bench - deno bundle - deno cache - deno compile - deno eval - deno install - deno test
2022-05-17BREAKING(unstable): Enable Deno namespace in workers by default (#14581)Nayeem Rahman
This commit removes "WorkerOptions.deno" option as a boolean, as well as "WorkerOptions.deno.namespace" settings. Starting with this commit all workers have access to "Deno" namespace by default.
2022-05-17BREAKING: Remove unstable Deno.emit and Deno.formatDiagnostics APIs (#14463)Bartek Iwańczuk
2022-05-17fix: base64 encoding of source maps with emojis (#14607)Bartek Iwańczuk
This commit fixes source maps for files that contain emojis. This is done by updating "deno_ast" to "0.14.1" for the case of "--no-check" flag (ie using SWC emit) and by overriding TSC's default base64 encoder (which turned out to be buggy) for the type checking case.
2022-05-16feat(ext/net): add `CAA` DNS record support in Deno.resolveDns() API (#14624)Craig Morten
2022-05-15feat(ext/net): support NAPTR records in Deno.resolveDns() API (#14613)Craig Morten
2022-05-15feat(ext/net): support full `SOA` record interface (#14617)Craig Morten
2022-05-14feat(ext/net): add support for SOA records in Deno.resolveDns() API (#14534)Thanapat Chotipun
2022-05-13feat: add --no-config flag (#14555)Bartek Iwańczuk
This flag disables loading of configuration file, ie. it will not be automatically discovered and loaded. Of course this flag conflicts with "--config" flag and they cannot be used together.
2022-05-13chore: update test_util/std/ submodule (#14595)Bartek Iwańczuk
2022-05-11chore: fix flaky integration::test::pass test (#14571)David Sherret
2022-05-10fix(runtime/web_worker): Use biased select when getting module result (#14553)Nayeem Rahman
2022-05-09feat(test): repeat test name if there's user output (#14495)Bartek Iwańczuk
This commit changes test report output to repeat test name before printing result, but only if there's user output, denoted by markers.
2022-05-09feat(test): Represent uncaught errors (#14513)Nayeem Rahman
This commit adds better reporting of uncaught errors in top level scope of testing files. This change affects both console runner as well as LSP runner.
2022-05-09feat(test): change "failures:" headers in test report (#14490)Bartek Iwańczuk
2022-05-08fix(core): avoid panic on non-string Error.name (#14529)Aaron O'Mullan
Fixes #14518
2022-05-07refactor(core): add AssertedModuleType enum (#14501)Bartek Iwańczuk
Co-authored-by: Luca Casonato <hello@lcas.dev>
2022-05-05feat(test): Show Deno.test() call locations for failures (#14484)Nayeem Rahman
2022-05-05test: Manually truncate path string (#14407)Nayeem Rahman
2022-05-04fix(coverage): exclude .snap files (#14480)Geert-Jan Zwiers
2022-05-03feat(ext/net): add "NS" record support in Deno.resolveDns API (#14372)Thanapat Chotipun
2022-05-02fix(test/bench): accept file protocol module specifier CLI args (#14429)Adilson Schmitt Junior
2022-05-01fix(test): actually capture stdout and stderr in workers (#14435)David Sherret
2022-04-29fix(cli): add dom.extras lib (#14430)Kitson Kelly
Closes: #12558 Fixes: #14344
2022-04-27fix(workers): Make `worker.terminate()` not block the current thread (#13941)Andreu Botella
Calling `worker.terminate()` used to kill the worker's isolate and then block until the worker's thread finished. This blocks the calling thread if the worker's event loop was blocked in a sync op (as with `Deno.sleepSync`), which wasn't realized at the time, but since the worker's isolate was killed at that moment, it would not block the calling thread if the worker was in a JS endless loop. However, in #12831, in order to work around a V8 bug, worker termination was changed to first set a signal to let the worker event loop know that termination has been requested, and only kill the isolate if the event loop has not finished after 2 seconds. However, this change kept the blocking, which meant that JS endless loops in the worker now blocked the parent for 2 seconds. As it turns out, after #12831 it is fine to signal termination and even kill the worker's isolate without waiting for the thread to finish, so this change does that. However, that might leave the async ops that receive messages and control data from the worker pending after `worker.terminate()`, which leads to odd results from the op sanitizer. Therefore, we set up a `CancelHandler` to cancel those ops when the worker is terminated.
2022-04-27refactor: Remove PrettyJsError and js_error_create_fn (#14378)Nayeem Rahman
This commit: - removes "fmt_errors::PrettyJsError" in favor of "format_js_error" fn - removes "deno_core::JsError::create" and "deno_core::RuntimeOptions::js_error_create_fn" - adds new option to "deno_runtime::ops::worker_host::init"
2022-04-26fix(test): capture worker stdout and stderr in test output (#14410)David Sherret
2022-04-26fix(test): capture inherited stdout and stderr for subprocesses in test ↵David Sherret
output (#14395)
2022-04-24fix(runtime/js/spawn): Pass stdio options for spawn() and spawnSync() (#14358)Nayeem Rahman
2022-04-23fix(bench): report pending summary before clearing (#14369)evan
2022-04-22fix(bench): reset reporter context (#14360)evan
This commit fixes previous file benchmarks leaking into the next file benchmarks summary.
2022-04-20feat(bench): update API, new console reporter (#14305)evan
This commit changes "deno bench" subcommand, by updating the "Deno.bench" API as follows: - remove "Deno.BenchDefinition.n" - remove "Deno.BenchDefintion.warmup" - add "Deno.BenchDefinition.group" - add "Deno.BenchDefintion.baseline" This is done because bench cases are no longer run fixed amount of iterations, but instead they are run until there is difference between subsequent runs that is statistically insiginificant. Additionally, console reporter was rewritten completely, to looks similar to "hyperfine" reporter.
2022-04-19Remove the DENO_FUTURE_CHECK warning (#14320)Luca Casonato
It has good intentions, but it is a really terrible user experience. As such we shouldn't print this warning.
2022-04-19feat(ext/web): add globalThis.reportError() (#13799)Nayeem Rahman
2022-04-18feat: Add DENO_NO_PROMPT variable (#14209)Nayeem Rahman
This commit adds support for "DENO_NO_PROMPT" env variable, that can be used instead of "--no-prompt" flag to completely disable permission prompts.
2022-04-18fix(cli/emit): Check JS roots with // @ts-check (#14090)Nayeem Rahman
2022-04-18feat(test): skip internal stack frames for errors (#14302)Bartek Iwańczuk
This commit changes "deno test" to filter out stack frames if it is beneficial to the user. This is the case when there are stack frames coming from "internal" code below frames coming from user code. Co-authored-by: Nayeem Rahman <nayeemrmn99@gmail.com>
2022-04-17fix: panic when trying to pledge permissions before restoring previous ↵Bartek Iwańczuk
pledge (#14306) This commit fixes and edge case, where testing/benching code could pledge new permission set before restoring the previous pledge. Appropriate panics were added and tests that assert that process is killed in case of "recursive pledge".