Age | Commit message (Collapse) | Author |
|
Fixes #10747
|
|
|
|
Fixes #10775
|
|
Fixes #10815
|
|
Closes: #10194
Fixes: #10468
|
|
|
|
Fixes #10168
Fixes #10615
Fixes #10616
|
|
Fixes #10765
|
|
|
|
|
|
Fixes #9823
|
|
Fixes #10603
|
|
Fixes #10695
|
|
|
|
Closes #9932
|
|
Resolves #9447
Resolves #9415
|
|
|
|
Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
|
|
|
|
|
|
|
|
Landed without test to meet 1.10.0 deadline. See #10587.
|
|
Ref: #10368
|
|
|
|
|
|
(#10481)
Currently file passed to --config file is parsed using TsConfig structure
that does multiple things when loading the file. Instead of relying on that
structure I've introduced ConfigFile structure that can be updated to
sniff out more fields from the config file in the future.
|
|
Ref #8643
|
|
Resolves #10518
|
|
(#10448)
|
|
Makes the codebase more searchable and helps distinguish op functions from helper functions
Besides tests/examples/benches this pattern appears to be used everywhere else in the codebase
|
|
Fixes #10444
|
|
|
|
Fixes #10362
|
|
Even if bootstrapping the JS runtime is low level, it's an abstraction leak of
core to require users to call `Deno.core.ops()` in JS space.
So instead we're introducing a `JsRuntime::sync_ops_cache()` method,
once we have runtime extensions a new runtime will ensure the ops
cache is setup (for the provided extensions) and then loading/unloading
plugins should be the only operations that require op cache syncs
|
|
(#10196)
Closes: #10118
|
|
|
|
|
|
properly (#10261)
|
|
Co-authored-by: Kitson Kelly <me@kitsonkelly.com>
|
|
Co-authored-by: Kitson Kelly <me@kitsonkelly.com>
|
|
Fixes #10125
|
|
|
|
|
|
1. error: called `.iter().count()` on a `Vec`
2. error: inconsistent struct constructor
|
|
|
|
Co-authored-by: Yoshiya Hinosawa <stibium121@gmail.com>
Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
|
|
Fixes: #9773
|
|
|
|
|
|
Fixes: #9744
Fixes: https://github.com/denoland/vscode_deno/issues/386
|