Age | Commit message (Collapse) | Author |
|
Missed in https://github.com/denoland/deno/pull/22277
|
|
These are not useful, as we bench them in `deno_core` already.
|
|
Brings the number of ops exposed to user code down to 58.
|
|
This moves the op sanitizer descriptions into Rust code and prepares for
eventual op import from `ext:core/ops`. We cannot import these ops from
`ext:core/ops` as the testing infrastructure ops are not always present.
Changes:
- Op descriptions live in `cli` code and are currently accessible via an
op for the older sanitizer code
- `phf` dep moved to workspace root so we can use it here
- `ops.op_XXX` changed to to `op_XXX` to prepare for op imports later
on.
|
|
Originally in #22125
Reverted in #22153 because of #22148
Fixed in deno_core https://github.com/denoland/deno_core/pull/538
Test plan:
1. Check out: https://github.com/poolifier/poolifier-deno.git
2. `PATH=.../deno/target/release/:$PATH deno task test`
3. `ok | 13 passed (188 steps) | 0 failed (18s)`
|
|
Extract zero-risk changes from #22226
|
|
This is a followup on denoland/deno_core#471.
Fixes #21439.
|
|
Check that in a `KvListSelector`, `start` and `end` are actually within
the keyspace bounds defined by `prefix`, if both are present.
|
|
|
|
(#22235)
Closes #22178.
|
|
This test should be in `deno_core`.
Ref https://github.com/denoland/deno_core/issues/533
|
|
Micro-optimization.
|
|
Closes #22239
|
|
Signed-off-by: Dan Rose <danoftheroses@gmail.com>
|
|
Signed-off-by: Asher Gomez <ashersaupingomez@gmail.com>
Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
|
|
Alternative to https://github.com/denoland/deno/pull/22223 which
switches `webbrowser` crate to `open` (https://crates.io/crates/open)
which is lighterweight.
|
|
This is the release commit being forwarded back to main for 1.40.3
Ref https://github.com/denoland/deno/pull/22219
|
|
Fixes https://github.com/denoland/deno/issues/22211
|
|
|
|
This commit adds `ppid` getter for `node:process` to improve Node
compatibility one step further.
There is one problem though, which is that `Deno.ppid`, which
`process.ppid` internally calls, is actually of type `bigint` although
it's supposed to be `number`. I filed an issue for this (#22166). For
the time being, explciit type conversion from `bigint` to `number` is
applied to match the Node.js behavior.
|
|
Closes https://github.com/denoland/deno/issues/22154
|
|
Towards #21804
|
|
Fixes https://github.com/denoland/deno/issues/22180
Matches the Node.js implementation more closely. Removed types, they do
not help just make it harder to debug with stack traces.
|
|
Upgrades deno_graph to 0.64 where deno_graph is now responsible for
turning bytes into a string. This is in preparation for Wasm modules.
|
|
Also prints an information about the flag when there are `zap` errors.
|
|
|
|
This commit adds a list of ops to `runtime/99_main.js` that are
currently relying on getting them from `Deno.core.ops`. All ops that are not
present in the list are removed from `Deno.core.ops` on startup (they are
imported from "virtual op module" - `ext:core/ops`) making them effectively
inaccessible to user code.
This change lowers the number of ops exposed to user code from 650 to
around 260. This number should be gradually decreased in follow-up PRs.
|
|
|
|
|
|
This is super flaky on new Mac ARM runner. Disabling for now to unblock
main branch.
|
|
|
|
This doesn't actually trigger the arm64 build job nightly yet. I'll do
that in a follow up.
|
|
|
|
property (#22179)
Closes https://github.com/denoland/deno/issues/22176 (see detail there)
|
|
Fixes #22166
|
|
|
|
|
|
|
|
(#22147)
It makes it easier to write a standalone bin target for `deno compile`
without pulling a lot of the tooling and tsc loader logic
|
|
|
|
Step 1 of the Rustification of sanitizers, which unblocks the faster
timers.
This replaces the resource sanitizer with a Rust one, using the new APIs
in deno_core.
|
|
Co-authored-by: denobot <33910674+denobot@users.noreply.github.com>
Co-authored-by: bartlomieju <bartlomieju@users.noreply.github.com>
|
|
This commit makes deprecation warnings less verbose by default.
Only a single warnings is issued per deprecated API use.
`DENO_VERBOSE_WARNINGS` env var can be provided to enable more detailed
logging for each use of API including a stack trace.
https://github.com/denoland/deno/assets/13602871/9c036c84-0044-4cb6-9c8e-deb641f43712
|
|
|
|
|
|
|
|
Closes https://github.com/denoland/deno/issues/22116
|
|
Regression caused by https://github.com/denoland/deno/pull/22072.
I added a relevant test so we don't regress again.
Fixes https://github.com/denoland/deno/issues/22115
|
|
No code changes -- just splitting 40_testing into three files and
removing a couple of unused lines of code.
|
|
Co-authored-by: denobot <33910674+denobot@users.noreply.github.com>
Co-authored-by: bartlomieju <bartlomieju@users.noreply.github.com>
|