mirror of
https://github.com/denoland/deno.git
synced 2024-11-22 15:06:54 -05:00
692738232b
<!-- Before submitting a PR, please read https://deno.com/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. --> We were missing the `constants` export in the promise `fs` API which is available in node. ```ts import { constants, promises } from "node:fs"; import { constants as fsPromiseConstants } from "node:fs/promises"; console.log(constants === promises.constants); // logs: true console.log(constants === fsPromiseConstants); // logs: true ``` Fixes https://github.com/denoland/deno/issues/21994 |
||
|---|---|---|
| .. | ||
| benchmarks | ||
| ops | ||
| polyfills | ||
| analyze.rs | ||
| build.rs | ||
| Cargo.toml | ||
| clippy.toml | ||
| errors.rs | ||
| global.rs | ||
| lib.rs | ||
| package_json.rs | ||
| path.rs | ||
| polyfill.rs | ||
| README.md | ||
| resolution.rs | ||
deno_node
require and other node related functionality for Deno.