summaryrefslogtreecommitdiff
path: root/tests
AgeCommit message (Collapse)Author
2024-09-03fix(install): recommend using `deno install -g` when using a single http url ↵Bartek Iwańczuk
(#25388) Closes https://github.com/denoland/deno/issues/25361
2024-09-03chore: deprecate eval itests (#25382)HasanAlrimawi
This PR serves as a part of #22907 . --------- Signed-off-by: David Sherret <dsherret@users.noreply.github.com> Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com> Co-authored-by: David Sherret <dsherret@users.noreply.github.com>
2024-09-03fix(task): correct name for scoped npm package binaries (#25390)David Sherret
This is for when not using a node_modules directory or when using auto install for a node_modules dir.
2024-09-03test: fix info::info_import_map test (#25389)Bartek Iwańczuk
esm.sh provided a fix for `window` not existing in Deno anymore.
2024-09-03BREAKING(io): remove `Deno.copy()` (#25345)Asher Gomez
Towards #22079 --------- Signed-off-by: Asher Gomez <ashersaupingomez@gmail.com>
2024-09-03test: reenable frozen_lockfile tests (#25381)Bartek Iwańczuk
Ref https://github.com/denoland/deno/issues/25241
2024-09-03BREAKING(permissions): remove --allow-hrtime (#25367)Luca Casonato
Remove `--allow-hrtime` and `--deny-hrtime`. We are doing this because it is already possible to get access to high resolution timers through workers and SharedArrayBuffer. Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
2024-09-03fix: only enable byonm if workspace root has pkg json (#25379)David Sherret
Closes #25355
2024-09-03BREAKING(console): remove `Deno.customInspect` (#25348)Asher Gomez
Note: this is implemented on Deploy. However, according to @magurotuna, a thin compatibility layer might be in the works that'd prevent breakages for PRs such as this one. Towards #22079
2024-09-03BREAKING(unstable): drop support for Deno.run.{clearEnv,gid,uid} (#25371)Bartek Iwańczuk
These are unstable options and the APIs is now deprecated. To limit amount of unstable flags we elected to have these APIs removed.
2024-09-03fix: make some warnings more standard (#25324)David Sherret
2024-09-03chore(fs): remove `Deno.flock[Sync]()` (#25350)Asher Gomez
Towards #22079
2024-09-03feat: support DENO_LOG env var instead of RUST_LOG (#25356)Bartek Iwańczuk
Instead of `RUST_LOG` env var, we now support `DENO_LOG` env var. This is done to be able to set a setting specific to `deno` that wouldn't impact other binaries written in Rust. Ref https://github.com/denoland/deno/issues/10558#issuecomment-2324300211
2024-09-03BREAKING(io): remove `Deno.iter[Sync]()` (#25346)Asher Gomez
Towards #22079
2024-09-03BREAKING: remove `Deno.close()` (#25347)Asher Gomez
Towards #22079
2024-09-03BREAKING: remove `deno vendor` (#25343)Asher Gomez
2024-09-02fix(cli/tools): correct `deno init --serve` template behavior (#25318)Coty
2024-09-02BREAKING: remove `--allow-none` flag (#25337)Asher Gomez
Towards #22079 Signed-off-by: Luca Casonato <hello@lcas.dev> Co-authored-by: Luca Casonato <hello@lcas.dev>
2024-09-02feat(lsp): html/css/yaml file formatting (#25353)Nayeem Rahman
2024-09-02BREAKING: remove `--trace-ops` (#25344)Asher Gomez
Towards #22079
2024-09-02fix: remove entrypoint hack for Deno 2.0 (#25332)David Sherret
2024-09-02BREAKING: remove `deno bundle` (#25339)Asher Gomez
`deno bundle` now produces: ``` error: ⚠️ `deno bundle` was removed in Deno 2. See the Deno 1.x to 2.x Migration Guide for migration instructions: https://docs.deno.com/runtime/manual/advanced/migrate_deprecations ``` `deno bundle --help` now produces: ``` ⚠️ `deno bundle` was removed in Deno 2. See the Deno 1.x to 2.x Migration Guide for migration instructions: https://docs.deno.com/runtime/manual/advanced/migrate_deprecations Usage: deno bundle [OPTIONS] Options: -q, --quiet Suppress diagnostic output --unstable Enable all unstable features and APIs. Instead of using this flag, consider enabling individual unstable features To view the list of individual unstable feature flags, run this command again with --help=unstable ```
2024-09-02BREAKING: remove `--jobs` flag (#25336)Asher Gomez
2024-08-31chore: cleanup code for unstable tests (#25330)Bartek Iwańczuk
Towards https://github.com/denoland/deno/issues/25241 Removes code for tests of unstable APIs that were stabilized with Deno 2.0.0-rc.0.
2024-08-31chore: remove DENO_FUTURE=1 from spec tests (#25329)Bartek Iwańczuk
Towards https://github.com/denoland/deno/issues/25241
2024-08-31chore(fs): remove `Deno.futime[Sync]()` (#25252)Asher Gomez
2024-08-31fix(upgrade): more informative information on invalid version (#25319)Bartek Iwańczuk
Before: ``` $ deno upgrade v1.xx error: Invalid version passed ``` After: ``` $ deno upgrade v1.xx error: Invalid version passed (v1.xx) Example usage: deno upgrade | deno upgrade 1.46 | deno upgrade canary ``` Also updates help text to use "shorthand version" without flags, but a positional arg.
2024-08-31chore(net): remove `Deno.shutdown()` (#25253)Asher Gomez
2024-08-31chore: remove `Deno.resources()` (#25251)Asher Gomez
2024-08-31chore: remove `Deno.metrics()` (#25167)Asher Gomez
2024-08-30fix(lint): support linting jsr pkg without version field (#25230)David Sherret
2024-08-30refactor: remove DENO_FUTURE (#25314)David Sherret
2024-08-30fix: upgrade deno_ast 0.42 (#25313)David Sherret
2024-08-30BREAKING: `DENO_FUTURE=1` by default, or welcome to Deno 2.0 (#25213)Bartek Iwańczuk
This commit effectively turns Deno into Deno 2.0. This is done by forcing `DENO_FUTURE=1` env var, that was available in the past few months to try Deno 2 changes. This commit contains several breaking changes scheduled for Deno 2: - all deprecated JavaScript APIs are not available any more, mostly `Deno.*` APIs - `window` global is removed - FFI, WebGPU and FS APIs are now stable and don't require `--unstable-*` flags - import assertions are no longer supported - "bring your own node modules" is enabled by default This is the first commit in a series that are scheduled before the Deno 2 release. Follow up work is tracked in https://github.com/denoland/deno/issues/25241. --------- Co-authored-by: Asher Gomez <ashersaupingomez@gmail.com> Co-authored-by: Nayeem Rahman <nayeemrmn99@gmail.com> Co-authored-by: Nathan Whitaker <nathan@deno.com>
2024-08-30fix(ext/node): session close during stream setup (#25170)Caleb Lloyd
Signed-off-by: Caleb Lloyd <caleblloyd@gmail.com>
2024-08-30test(ext/node): check hostname option has precedence over host option (#25292)Yoshiya Hinosawa
2024-08-29feat(config): Node modules option for 2.0 (#25299)Nathan Whitaker
2024-08-29fix: reland async context (#25140)snek
This reverts commit 71ca61e189cca9215982ce4598b7a4da8430c584. Now uses a shared implementation from deno_core.
2024-08-29fix: upgrade deno_core to 0.307.0 (#25287)snek
- fix for https://github.com/denoland/deno/issues/25160 - changes needed to land https://github.com/denoland/deno/pull/25140
2024-08-28fix(permissions): disallow any `LD_` or `DYLD_` prefixed env var without ↵David Sherret
full --allow-run permissions (#25271) Follow up to https://github.com/denoland/deno/pull/25221 I looked into what the list was and it was quite extensive, so I think as suggested in https://github.com/denoland/deno/issues/11964#issuecomment-2314585135 we should disallow this for any `LD_` prefixed env var.
2024-08-29feat: deprecate import assertions (#25281)David Sherret
Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
2024-08-29test: run specs::npm::exec_file_inside_npm_package with DENO_FUTURE=1 (#25282)Bartek Iwańczuk
The test is failing if run with `DENO_FUTURE=1` which is blocking https://github.com/denoland/deno/pull/25213. --------- Co-authored-by: David Sherret <dsherret@gmail.com>
2024-08-29test: run `node_unit_tests` with `DENO_FUTURE=1` (#25285)Bartek Iwańczuk
This is blocking https://github.com/denoland/deno/pull/25213. Turns out a bunch of FS APIs are completely broken because they use RIDs (resource IDs) instead of FDs (file descriptors).
2024-08-29test: replace usage of `window` with `globalThis` (#25284)Bartek Iwańczuk
Fixes several tests blocking https://github.com/denoland/deno/pull/25213 by replacing `window` global that is gone in Deno 2 with `globalThis`. Also adjusted a few tests using deprecated `rid` field.
2024-08-28test: Don't run unit tests with and without `DENO_FUTURE=1` (#25273)Bartek Iwańczuk
This is still flaky and won't be needed anyway once https://github.com/denoland/deno/pull/25213 lands.
2024-08-28refactor: don't virtualize the `console` global for node mode (#25263)Luca Casonato
Turns out we only virtualized it so one could have a `Console` property, and the other one not. We can just make this `console.Console` available everywhere.
2024-08-28feat: improve lockfile v4 to store normalized version constraints and be ↵David Sherret
more terse (#25247) Stores normalized version constraints in the lockfile, which will improve reproducibility and will fix a bug with duplicate specifiers ending up in the lockfile. Also, gets rid of some duplicate data in the specifiers area of the lockfile.
2024-08-28fix(napi): Fix worker threads importing already-loaded NAPI addon (#25245)Nathan Whitaker
Part of #20613. If a node addon is using the legacy `napi_module_register` on ctor approach to module registration, we have to store the registered module so that other threads can load the addon (because `napi_module_register` will only be called once per process).
2024-08-28fix(ext/node): import RSA JWK keys (#25267)Divy Srivastava
Fixes https://github.com/denoland/deno/issues/24129
2024-08-28fix(ext/node): export JWK public key (#25239)Divy Srivastava
Fixes https://github.com/denoland/deno/issues/18928 Signed-off-by: Divy Srivastava <dj.srivastava23@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-21 02:02:31 +0000