Age | Commit message (Collapse) | Author | |
---|---|---|---|
2024-09-10 | feat(cli): use NotCapable error for permission errors (#25431) | Luca Casonato | |
Closes #7394 --------- Co-authored-by: snek <snek@deno.com> | |||
2024-09-05 | feat(check): turn on useUnknownInCatchVariables (#25465) | David Sherret | |
Part of #25162 Closes #11826 | |||
2024-08-19 | chore: improve accessing special file test (#25099) | David Sherret | |
2024-07-02 | fix(ext/node): Add `fs.lutimes` / `fs.lutimesSync` (#23172) | Nathan Whitaker | |
Part of #18218 - Adds `fs.lutimes` and `fs.lutimesSync` to our node polyfills. To do this I added methods to the `FileSystem` trait + ops to expose the functionality to JS. - Exports `fs._toUnixTimestamp`. Node exposes an internal util `toUnixTimestamp` from the fs module to be used by unit tests (so we need it for the unit test to pass unmodified). It's weird because it's only supposed to be used internally but it's still publicly accessible - Matches up error handling and timestamp handling for fs.futimes and fs.utimes with node - Enables the node_compat utimes test - this exercises futimes, lutimes, and utimes. | |||
2024-04-19 | feat(runtime): Allow embedders to perform additional access checks on file ↵ | Matt Mastracci | |
open (#23208) Embedders may have special requirements around file opening, so we add a new `check_open` permission check that is called as part of the file open process. | |||
2024-02-10 | chore: move cli/tests/ -> tests/ (#22369) | Matt Mastracci | |
This looks like a massive PR, but it's only a move from cli/tests -> tests, and updates of relative paths for files. This is the first step towards aggregate all of the integration test files under tests/, which will lead to a set of integration tests that can run without the CLI binary being built. While we could leave these tests under `cli`, it would require us to keep a more complex directory structure for the various test runners. In addition, we have a lot of complexity to ignore various test files in the `cli` project itself (cargo publish exclusion rules, autotests = false, etc). And finally, the `tests/` folder will eventually house the `test_ffi`, `test_napi` and other testing code, reducing the size of the root repo directory. For easier review, the extremely large and noisy "move" is in the first commit (with no changes -- just a move), while the remainder of the changes to actual files is in the second commit. |