Age | Commit message (Collapse) | Author |
|
Towards #22079
Signed-off-by: Asher Gomez <ashersaupingomez@gmail.com>
|
|
Towards #22079
Signed-off-by: Asher Gomez <ashersaupingomez@gmail.com>
|
|
Towards #22079
|
|
|
|
Aligns the error messages in the cli/js folder to be in-line with the
Deno style guide.
|
|
|
|
Aligns the error messages in the ext/fetch folder to be in-line with the
Deno style guide.
https://github.com/denoland/deno/issues/25269
|
|
Co-authored-by: crowlkats <crowlkats@toaxl.com>
|
|
Towards #22079
Signed-off-by: Asher Gomez <ashersaupingomez@gmail.com>
|
|
(#25391)
Also rewrites some of the subcommands help text
Closes https://github.com/denoland/deno/issues/25362
---------
Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
|
|
(#25388)
Closes https://github.com/denoland/deno/issues/25361
|
|
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>
|
|
This is for when not using a node_modules directory or when using auto
install for a node_modules dir.
|
|
esm.sh provided a fix for `window` not existing in Deno anymore.
|
|
Towards #22079
---------
Signed-off-by: Asher Gomez <ashersaupingomez@gmail.com>
|
|
Ref https://github.com/denoland/deno/issues/25241
|
|
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>
|
|
Closes #25355
|
|
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
|
|
These are unstable options and the APIs is now deprecated. To limit
amount of unstable flags we elected to have these APIs removed.
|
|
|
|
Towards #22079
|
|
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
|
|
Towards #22079
|
|
Towards #22079
|
|
|
|
|
|
Towards #22079
Signed-off-by: Luca Casonato <hello@lcas.dev>
Co-authored-by: Luca Casonato <hello@lcas.dev>
|
|
|
|
Towards #22079
|
|
|
|
`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
```
|
|
|
|
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.
|
|
Towards https://github.com/denoland/deno/issues/25241
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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>
|
|
Signed-off-by: Caleb Lloyd <caleblloyd@gmail.com>
|
|
|
|
|
|
This reverts commit 71ca61e189cca9215982ce4598b7a4da8430c584.
Now uses a shared implementation from deno_core.
|
|
- fix for https://github.com/denoland/deno/issues/25160
- changes needed to land https://github.com/denoland/deno/pull/25140
|
|
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.
|