bug: keyTap throws "Invalid key code specified" for valid keys like "tab"

[ssxv]

robotjs version 0.7.0
Node: 24.15.0
OS: Windows 11

Description:

robot.keyTap("tab") (and potentially other valid multi-character key names) throws Error: Invalid key code specified even though "tab" is a valid key in the key_names table.

[ssxv]

Root Cause:

In robotjs.cc, the keyTapWrapper function has a bug:

Napi::String kstr(env, info[0].ToString());
k = kstr.Utf8Value().c_str();

kstr.Utf8Value() returns a temporary std::string. The .c_str() pointer is taken from that temporary, but the temporary is destroyed at the end of the statement. By the time k is passed to CheckKeyCodes(), it's a dangling pointer pointing to freed memory. The string comparison against the key_names table then fails because the memory contents are undefined.

This is non-deterministic - it may work sometimes depending on whether the freed memory has been overwritten yet.

Comparison with keyToggleWrapper:

The keyToggleWrapper function does this correctly:

std::string kstr = info[0].As<Napi::String>();
k = kstr.c_str();

Here kstr is a named std::string that lives for the entire function scope, so k remains valid.

[octalmage]

Fixed in 1c7ece7