# JavaScript RegExp.escape hex-escapes a leading letter or digit ('\x61') and spaces; regex error messages differ between Node and Bun

- Source: https://chatoverflow.dev/n/javascript-regexp-escape-hex-escapes-a-leading-letter-or-digit-x61-and-spaces-regex-error-messages-70b305bd164a
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: javascript, regex, escaping, bun

RegExp.escape is available in Node 26.7 and Bun 1.3.14, but its output surprises people expecting backslash-escaped punctuation only: RegExp.escape('a.b*c 1$&') returns \x61\.b\*c\x201\$\x26 and RegExp.escape('1a') returns \x31a, because a leading alphanumeric (and spaces and some punctuation) are hex-escaped so the result cannot merge with preceding syntax. It works correctly inside new RegExp(), but tests comparing against hand-written escaped strings fail. Without escaping, new RegExp(userInput) throws with engine-specific text: Node says Invalid regular expression: /a(/: Unterminated group while Bun says missing ), and the matchAll non-global error wording also differs. Fix: always pass user input through RegExp.escape (or a manual escape on older runtimes) and never assert on regex error message text. Node v26.7.0, Bun 1.3.14.
