| Age | Commit message (Collapse) | Author |
|---|
|
(#18018)
JavaScript APIs from "runtime/js/40_files.js" combined abstractions
for stdio streams ("Stdout", "Stderr", "Stdin") and file system file
("File", "FsFile"). APIs from "runtime/js/40_read_file.js" and
"runtime/js/40_write_file.js" were implemented using ops from
"runtime/ops/fs.rs".
This file was removed and relevant APIs were moved to "deno_io/12_io.js"
and "runtime/js/30_fs.js".
This work is meant to enable factoring out "deno_fs" crate.
|
|
This file was not used anywhere - even though it exposed an unstable
"Deno.DiagnosticCategory" API. Seems like a left over from when we
had "Deno.emit" API.
|
|
(#18019)
This commit changes "include_js_files!" macro from "deno_core"
in a way that "dir" option doesn't cause specifiers to be rewritten
to include it.
Example:
```
include_js_files! {
dir "js",
"hello.js",
}
```
The above definition required embedders to use:
`import ... from "internal:<ext_name>/js/hello.js"`.
But with this change, the "js" directory in which the files are stored
is an implementation detail, which for embedders results in:
`import ... from "internal:<ext_name>/hello.js"`.
The directory the files are stored in, is an implementation detail and
in some cases might result in a significant size difference for the
snapshot. As an example, in "deno_node" extension, we store the
source code in "polyfills" directory; which resulted in each specifier
to look like "internal:deno_node/polyfills/<module_name>", but with
this change it's "internal:deno_node/<module_name>".
Given that "deno_node" has over 100 files, many of them having
several import specifiers to the same extension, this change removes
10 characters from each import specifier.
|
|
denoland/eszip#115 added support for statically-analyzed dynamic imports
in eszip, which made `deno compile` support dynamic imports starting
from #17858. This PR adds a test for it.
----
This test is adapted from PR #17663.
Closes #17908
|
|
|
|
This is a prerequisite to factor out FS ops to a separate crate.
|
|
This utility is useful in several contexts so it seems reasonable to
have it in `deno_core`.
|
|
This will help us with moving fs ops to a separate extension crate.
|
|
|
|
|
|
Closes #17941
|
|
|
|
When I was testing the code in #17892 I had updated expectations and
didn't catch this.
This PR fixes the the expectation file format to not be checked when
--no-ignore is passed during
[nightly](https://github.com/denoland/deno/actions/runs/4319520368/jobs/7538796572#step:9:46)
runs.
|
|
Reland https://github.com/denoland/deno/pull/16777
The codegen is disabled in async ops and when fallback to slow call is
possible (return type is a Result) to avoid hitting this V8 bug:
https://github.com/denoland/deno/issues/17159
|
|
(#17892)
- relands #17872
- updates the timeouts to be re-configurable just for CI
- fixes `./tools/wpt.ts update`
- adds option not "ignore" during, applied to wpt epoch runs only
|
|
<!--
Before submitting a PR, please read http://deno.land/manual/contributing
1. Give the PR a descriptive title.
Examples of good title:
- fix(std/http): Fix race condition in server
- docs(console): Update docstrings
- feat(doc): Handle nested reexports
Examples of bad title:
- fix #7123
- update docs
- fix bugs
2. Ensure there is a related issue and it is referenced in the PR text.
3. Ensure there are tests that cover the changes.
4. Ensure `cargo test` passes.
5. Ensure `./tools/format.js` passes without changing files.
6. Ensure `./tools/lint.js` passes.
7. Open as a draft PR if your work is still in progress. The CI won't
run
all steps, but you can add '[ci]' to a commit message to force it to.
8. If you would like to run the benchmarks on the CI, add the 'ci-bench'
label.
-->
This commit updates deno_lint crate to 0.41.0. The new version contains
a braking change that requries a minor code fix here, which is also
addressed in this commit.
|
|
|
|
|
|
|
|
pointer defaults (#17959)
|
|
Start of adding test builders to simplify integration tests.
I only updated a few test files. We can complete upgrading over time.
|
|
|
|
We were unconditionally inserting npm specifiers into the lockfile,
marking it as "dirty" and requiring saving.
|
|
|
|
|
|
Resolves https://github.com/denoland/deno/issues/17962
|
|
(#17863)
|
|
|
|
|
|
|
|
https://github.com/denoland/deno/actions/runs/4267836955/jobs/7429836369
Closes #17946
|
|
Co-authored-by: David Sherret <dsherret@gmail.com>
|
|
|
|
Tests added to deno_graph, which were previously not there.
Closes #17932
|
|
This lazily does an "npm install" when any package name matches what's
found in the package.json or when running a script from package.json
with deno task.
Part of #17916
Closes #17928
|
|
Part of #17916
|
|
Applies suggestion from #17912
|
|
sometimes fail (#17923)
Closes #17918
|
|
Depends on #17924
Part of #17916
|
|
`--no-npm` (#17924)
Part of #17916
|
|
This was a regression that has already been broken for some time, but
that also became broken for when using an import map 1.31.
Closes #17914
|
|
|
|
Co-authored-by: bartlomieju <bartlomieju@users.noreply.github.com>
Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
|
|
|
|
Runtime generation of async op wrappers contributed to increased startup
time and core became unusable with
`--disallow-code-generation-from-strings` flag. The optimization only
affects very small microbenchmarks so this revert will not cause any
regressions.
|
|
Put it on a single line and remove coloring.
|
|
webidl.setlike (#17800)
|
|
For example `import * as test from "package/path.js"`
|
|
language server (#17891)
|
|
|
