| Age | Commit message (Collapse) | Author |
|---|
|
|
|
We run these on the free machines now.
Also cleans up some of our os and arch conditional step handling by
introducing a new `matrix.os` and `matrix.arch`.
|
|
|
|
Understandably accidentally caused by
https://github.com/denoland/deno/pull/22187
|
|
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
|
|
Follow up to #22157.
This leaves us with 4 usages of `ensureFastOps()` in `deno` itself.
There's also about 150 usages of `Deno.core.ops.<op_name>` left as well.
|
|
Follow up to https://github.com/denoland/deno/pull/22135
|
|
|
|
|
|
|
|
Fixes #22150
|
|
(#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
|
|
|
|
First pass of migrating away from `Deno.core.ensureFastOps()`.
A few "tricky" ones have been left for a follow up.
|
|
|
|
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.
|
|
Now these props will not show up when inspecting objects in console.
|
|
Co-authored-by: Matt Mastracci <matthew@mastracci.com>
|
|
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>
|
|
Follow up to https://github.com/denoland/deno/pull/22040.
By mistake I forgot to disable "experimental decorators" in the LSP.
|
|
|
|
This reverts commit 971eb0e5e836cdeaaefc25b2bab4c6a6a9f8e213.
To unblock v1.40 release.
|
|
Bumped versions for 1.40.0
Co-authored-by: bartlomieju <bartlomieju@users.noreply.github.com>
Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
|
|
Co-authored-by: Asher Gomez <ashersaupingomez@gmail.com>
|
|
|
|
Otherwise, a deprecation warning will be printed.
|
|
Missed in #22077
|
|
This commit adds automatic expansion of "imports" field in "deno.json"
file.
If "npm:" or "jsr:" imports are encountered we automatically try to add
a "directory" remapping.
Previously users had to specify entries for both `foo` and `foo/` to be
able to import like
`import { symbol1 } from "foo";` and `import { symbol2 } from
"foo/some_file.js"`:
```
{
"imports": {
"foo": "npm:@foo/bar",
"foo/": "npm:/@foo/bar/",
}
```
With this change users can only add entry for `foo`:
```
{
"imports": {
"foo": "npm:@foo/bar",
}
```
The entry for `foo/` will be provided automatically.
Similarly if user provides "directory" remapping explicitly, we will not
overwrite it.
|
|
- `Deno.FsFile.dataSync` -> `Deno.FsFile.syncData`
- `Deno.FsFile.dataSyncSync` -> `Deno.FsFile.syncDataSync`
Also marks these APIs as unstable
|
|
|
|
|
|
For removal in Deno v2.
Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
|
|
|
|
|
|
This reverts commit 930ce2087051b4e45b2026ce7a77c14360a6993f.
This is producing false-positives that are not actionable to users.
We're gonna address this in another release.
|
|
For removal in Deno v2. There are two issues:
1. Any script being run causes the output of `warnOnDeprecatedApi()` to
be printed, even when none of the `rid` properties are called.
2. `.rid` of these classes is used in multiple tests. I'm not sure how
to account for that. I thought of having `STDIN_RID`, and friends,
constants, whose values can be shared between the tests and the classes
themselves. Should we go with that or do something else?
---------
Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
|
