Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: use more restrictive types for timingSafeEqual #936

Merged
merged 1 commit into from
Oct 22, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/lib/timing-safe-equal.js
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
import * as crypto from 'node:crypto'

/**
* @param {string | NodeJS.ArrayBufferView} value
* @returns {NodeJS.ArrayBufferView}
* @param {Readonly<string | Uint8Array>} value
* @returns {Uint8Array}
*/
const bufferify = (value) =>
// We use UTF-16 because it's the only supported encoding that doesn't
Expand All @@ -19,7 +19,7 @@ const bufferify = (value) =>
* Like `crypto.timingSafeEqual`, but works with strings and doesn't throw if
* lengths differ.
*
* @template {string | NodeJS.ArrayBufferView} T
* @template {string | Uint8Array} T
* @param {T} a
* @param {T} b
* @returns {boolean}
Expand Down
Loading