2023-02-14 11:38:45 -05:00
|
|
|
// Copyright 2018-2023 the Deno authors. All rights reserved. MIT license.
|
|
|
|
// Copyright Joyent, Inc. and Node.js contributors. All rights reserved. MIT license.
|
|
|
|
|
refactor(core): include_js_files! 'dir' option doesn't change specifiers (#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.
2023-03-04 21:31:38 -05:00
|
|
|
import { notImplemented } from "internal:deno_node/_utils.ts";
|
|
|
|
import { Buffer } from "internal:deno_node/buffer.ts";
|
2023-02-14 11:38:45 -05:00
|
|
|
import {
|
|
|
|
ERR_INVALID_ARG_TYPE,
|
|
|
|
hideStackFrames,
|
refactor(core): include_js_files! 'dir' option doesn't change specifiers (#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.
2023-03-04 21:31:38 -05:00
|
|
|
} from "internal:deno_node/internal/errors.ts";
|
2023-02-14 11:38:45 -05:00
|
|
|
import {
|
|
|
|
isAnyArrayBuffer,
|
|
|
|
isArrayBufferView,
|
refactor(core): include_js_files! 'dir' option doesn't change specifiers (#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.
2023-03-04 21:31:38 -05:00
|
|
|
} from "internal:deno_node/internal/util/types.ts";
|
|
|
|
import { crypto as constants } from "internal:deno_node/internal_binding/constants.ts";
|
2023-02-14 11:38:45 -05:00
|
|
|
import {
|
|
|
|
kHandle,
|
|
|
|
kKeyObject,
|
refactor(core): include_js_files! 'dir' option doesn't change specifiers (#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.
2023-03-04 21:31:38 -05:00
|
|
|
} from "internal:deno_node/internal/crypto/constants.ts";
|
2023-02-14 11:38:45 -05:00
|
|
|
|
|
|
|
// TODO(kt3k): Generate this list from `digestAlgorithms`
|
|
|
|
// of std/crypto/_wasm/mod.ts
|
|
|
|
const digestAlgorithms = [
|
|
|
|
"blake2b256",
|
|
|
|
"blake2b384",
|
|
|
|
"blake2b",
|
|
|
|
"blake2s",
|
|
|
|
"blake3",
|
|
|
|
"keccak-224",
|
|
|
|
"keccak-256",
|
|
|
|
"keccak-384",
|
|
|
|
"keccak-512",
|
|
|
|
"sha384",
|
|
|
|
"sha3-224",
|
|
|
|
"sha3-256",
|
|
|
|
"sha3-384",
|
|
|
|
"sha3-512",
|
|
|
|
"shake128",
|
|
|
|
"shake256",
|
|
|
|
"tiger",
|
|
|
|
"rmd160",
|
|
|
|
"sha224",
|
|
|
|
"sha256",
|
|
|
|
"sha512",
|
|
|
|
"md4",
|
|
|
|
"md5",
|
|
|
|
"sha1",
|
|
|
|
];
|
|
|
|
|
2023-02-20 11:52:28 -05:00
|
|
|
// deno-fmt-ignore
|
|
|
|
const supportedCiphers = [
|
|
|
|
"aes-128-ecb", "aes-192-ecb",
|
|
|
|
"aes-256-ecb", "aes-128-cbc",
|
|
|
|
"aes-192-cbc", "aes-256-cbc",
|
|
|
|
"aes128", "aes192",
|
|
|
|
"aes256", "aes-128-cfb",
|
|
|
|
"aes-192-cfb", "aes-256-cfb",
|
|
|
|
"aes-128-cfb8", "aes-192-cfb8",
|
|
|
|
"aes-256-cfb8", "aes-128-cfb1",
|
|
|
|
"aes-192-cfb1", "aes-256-cfb1",
|
|
|
|
"aes-128-ofb", "aes-192-ofb",
|
|
|
|
"aes-256-ofb", "aes-128-ctr",
|
|
|
|
"aes-192-ctr", "aes-256-ctr",
|
|
|
|
"aes-128-gcm", "aes-192-gcm",
|
|
|
|
"aes-256-gcm"
|
|
|
|
];
|
|
|
|
|
|
|
|
export function getCiphers(): string[] {
|
|
|
|
return supportedCiphers;
|
|
|
|
}
|
|
|
|
|
2023-02-14 11:38:45 -05:00
|
|
|
let defaultEncoding = "buffer";
|
|
|
|
|
|
|
|
export function setDefaultEncoding(val: string) {
|
|
|
|
defaultEncoding = val;
|
|
|
|
}
|
|
|
|
|
|
|
|
export function getDefaultEncoding(): string {
|
|
|
|
return defaultEncoding;
|
|
|
|
}
|
|
|
|
|
|
|
|
// This is here because many functions accepted binary strings without
|
|
|
|
// any explicit encoding in older versions of node, and we don't want
|
|
|
|
// to break them unnecessarily.
|
|
|
|
export function toBuf(val: string | Buffer, encoding?: string): Buffer {
|
|
|
|
if (typeof val === "string") {
|
|
|
|
if (encoding === "buffer") {
|
|
|
|
encoding = "utf8";
|
|
|
|
}
|
|
|
|
|
|
|
|
return Buffer.from(val, encoding);
|
|
|
|
}
|
|
|
|
|
|
|
|
return val;
|
|
|
|
}
|
|
|
|
|
|
|
|
export const validateByteSource = hideStackFrames((val, name) => {
|
|
|
|
val = toBuf(val);
|
|
|
|
|
|
|
|
if (isAnyArrayBuffer(val) || isArrayBufferView(val)) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
throw new ERR_INVALID_ARG_TYPE(
|
|
|
|
name,
|
|
|
|
["string", "ArrayBuffer", "TypedArray", "DataView", "Buffer"],
|
|
|
|
val,
|
|
|
|
);
|
|
|
|
});
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Returns an array of the names of the supported hash algorithms, such as 'sha1'.
|
|
|
|
*/
|
|
|
|
export function getHashes(): readonly string[] {
|
|
|
|
return digestAlgorithms;
|
|
|
|
}
|
|
|
|
|
|
|
|
export function getCurves(): readonly string[] {
|
|
|
|
notImplemented("crypto.getCurves");
|
|
|
|
}
|
|
|
|
|
|
|
|
export interface SecureHeapUsage {
|
|
|
|
total: number;
|
|
|
|
min: number;
|
|
|
|
used: number;
|
|
|
|
utilization: number;
|
|
|
|
}
|
|
|
|
|
|
|
|
export function secureHeapUsed(): SecureHeapUsage {
|
|
|
|
notImplemented("crypto.secureHeapUsed");
|
|
|
|
}
|
|
|
|
|
|
|
|
export function setEngine(_engine: string, _flags: typeof constants) {
|
|
|
|
notImplemented("crypto.setEngine");
|
|
|
|
}
|
|
|
|
|
2023-02-20 11:52:28 -05:00
|
|
|
export { kHandle, kKeyObject };
|
2023-02-14 11:38:45 -05:00
|
|
|
|
|
|
|
export default {
|
|
|
|
getDefaultEncoding,
|
|
|
|
getHashes,
|
|
|
|
setDefaultEncoding,
|
|
|
|
getCiphers,
|
|
|
|
getCurves,
|
|
|
|
secureHeapUsed,
|
|
|
|
setEngine,
|
|
|
|
validateByteSource,
|
|
|
|
toBuf,
|
|
|
|
kHandle,
|
|
|
|
kKeyObject,
|
|
|
|
};
|