oven-sh/bun

Hashing functions from `node:crypto` don't support the same inputs as Node.js

Open

#18,019 opened on Mar 9, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (90,348 stars) (4,486 forks)batch import
buggood first issuenode:crypto

Description

What version of Bun is running?

1.2.4+fd9a5ea66

What platform is your computer?

Linux 6.1.91-060191-generic x86_64 x86_64, the issues isn't platform specific

What steps can reproduce the bug?

The following code...

import crypto from "node:crypto"

console.log(crypto.hash("shake-128", "", "base64url"))

...runs successfully on node.js and logs...

> node x.js 
f5wrpOiPgn1hYEVQdgWFPg

However, Bun throws an error.

> bun x.js 
1 | import crypto from "node:crypto"
2 | 
3 | console.log(crypto.hash("shake-128", "", "base64url"))
                       ^
TypeError: Unsupported algorithm "shake-128"
 code: "ERR_INVALID_ARG_TYPE"

      at /workspace/x.js:3:20

Bun v1.2.4 (Linux x64)

Bun does support the actual algorithms. For example, using "shake128" (without the hyphen) does work. Bun does not support the same aliases as Node.js, creating interop issues.

What is the expected behavior?

Same as Node.js

What do you see instead?

ERR_INVALID_ARG_TYPE

Additional information

No response

Contributor guide

Tech stack
javascript
Domain
api
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
The issue is that Bun's crypto.hash does not support all algorithm name aliases that Node.js does, e.g., 'shake 128' vs 'shake128'. Look at the implementation of the crypto module in Bun, likely in src/js/node/crypto.js or a native file, to find where algorithm names are validated and mapped. Add missing aliases by referring to Node.js's supported algorithm names. The fix is localized and should involve adding the hyphenated variants to the list of supported algorithms.
Hashing functions from `node:crypto` don't support the same inputs as Node.js · oven-sh/bun#18019 | Good First Issue