toHaveProperty not working with semi-complex (but legal) property names

[CodexHere]

Describe the bug

On an object (logged before assertion), we can see some properties defined correctly, however when testing via expects assertions it fails incorrectly expecting undefined

expect(fixture).toHaveProperty('plugin-behavior-v1.0.0');

Returns Error:

ssertionError: expected { …(5) } to have property undefined

It seems either having more than 1 hyphen, or a combination of hyphen and period seems to break it?

Workaround is explicitly check toBeDefined like so:

  expect(fixture['plugin-behavior-v1.0.0']).toBeDefined();

Reproduction

https://stackblitz.com/edit/vitest-dev-vitest-bdcj2g?file=test%2Fbasic.test.ts&initialPath=__vitest__

System Info

(Running in Docker)

  System:
    OS: Linux 5.18 Alpine Linux
    CPU: (16) x64 AMD Ryzen 7 1700X Eight-Core Processor
    Memory: 19.72 GB / 31.28 GB
    Container: Yes
    Shell: 1.35.0 - /bin/ash
  Binaries:
    Node: 16.16.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.11.0 - /usr/local/bin/npm
  npmPackages:
    vitest: ^0.20.3 => 0.20.3

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.