mirror of
https://github.com/denoland/deno.git
synced 2024-11-29 16:30:56 -05:00
b40086fd7d
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.
65 lines
2.1 KiB
TypeScript
65 lines
2.1 KiB
TypeScript
// Copyright 2018-2023 the Deno authors. All rights reserved. MIT license.
|
|
// Forked from https://github.com/DefinitelyTyped/DefinitelyTyped/blob/d9df51e34526f48bef4e2546a006157b391ad96c/types/node/fs.d.ts
|
|
|
|
import { ErrnoException } from "internal:deno_node/_global.d.ts";
|
|
|
|
/**
|
|
* Write an array of `ArrayBufferView`s to the file specified by `fd` using`writev()`.
|
|
*
|
|
* `position` is the offset from the beginning of the file where this data
|
|
* should be written. If `typeof position !== 'number'`, the data will be written
|
|
* at the current position.
|
|
*
|
|
* The callback will be given three arguments: `err`, `bytesWritten`, and`buffers`. `bytesWritten` is how many bytes were written from `buffers`.
|
|
*
|
|
* If this method is `util.promisify()` ed, it returns a promise for an`Object` with `bytesWritten` and `buffers` properties.
|
|
*
|
|
* It is unsafe to use `fs.writev()` multiple times on the same file without
|
|
* waiting for the callback. For this scenario, use {@link createWriteStream}.
|
|
*
|
|
* On Linux, positional writes don't work when the file is opened in append mode.
|
|
* The kernel ignores the position argument and always appends the data to
|
|
* the end of the file.
|
|
* @since v12.9.0
|
|
*/
|
|
export function writev(
|
|
fd: number,
|
|
buffers: ReadonlyArray<ArrayBufferView>,
|
|
cb: (
|
|
err: ErrnoException | null,
|
|
bytesWritten: number,
|
|
buffers: ArrayBufferView[],
|
|
) => void,
|
|
): void;
|
|
export function writev(
|
|
fd: number,
|
|
buffers: ReadonlyArray<ArrayBufferView>,
|
|
position: number | null,
|
|
cb: (
|
|
err: ErrnoException | null,
|
|
bytesWritten: number,
|
|
buffers: ArrayBufferView[],
|
|
) => void,
|
|
): void;
|
|
export interface WriteVResult {
|
|
bytesWritten: number;
|
|
buffers: ArrayBufferView[];
|
|
}
|
|
export namespace writev {
|
|
function __promisify__(
|
|
fd: number,
|
|
buffers: ReadonlyArray<ArrayBufferView>,
|
|
position?: number,
|
|
): Promise<WriteVResult>;
|
|
}
|
|
/**
|
|
* For detailed information, see the documentation of the asynchronous version of
|
|
* this API: {@link writev}.
|
|
* @since v12.9.0
|
|
* @return The number of bytes written.
|
|
*/
|
|
export function writevSync(
|
|
fd: number,
|
|
buffers: ReadonlyArray<ArrayBufferView>,
|
|
position?: number,
|
|
): number;
|