Bug report There seems to be an issue while testing with vitest an

The root of the issue is with React 17: <a class="issue-link js-issue-link" data-e

facing a similar error <div class="snippet-clipboard-content notranslate position-

Failing tests with react testing library, vitest and react@17.0.1 ,about radix-ui/primitives

Comments (4)

vladmoroz commented on June 29, 2024 2

The root of the issue is with React 17:
facebook/react#20235
vitest-dev/vitest#2468

I'd recommend to upgrade to React 18 and also pin your dependencies as this most definitely sounds like an "accidental" upgrade:

This error started occurring in one of my company's private repos a couple of days ago. I ran workflows on commits that were previously not failing. They started failing out of nowhere with this exact error. We have not upgraded any versions of radix components at all these past days.

Otherwise have vitest resolve your @radix-ui deps instead of Node

test: {
  deps: {
    inline: [/@radix-ui/],
  },
}

from primitives.

nawed2611 commented on June 29, 2024

does upgrading react version work?

from primitives.

nawed2611 commented on June 29, 2024

facing a similar error

ERROR in ./node_modules/@radix-ui/react-tooltip/dist/index.mjs 18:0-46
Module not found: Error: Can't resolve 'react/jsx-runtime' in '/node_modules/@radix-ui/react-tooltip/dist'
Did you mean 'jsx-runtime.js'?
BREAKING CHANGE: The request 'react/jsx-runtime' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/@radix-ui/react-visually-hidden/dist/index.mjs 4:0-40
Module not found: Error: Can't resolve 'react/jsx-runtime' in '/node_modules/@radix-ui/react-visually-hidden/dist'
Did you mean 'jsx-runtime.js'?
BREAKING CHANGE: The request 'react/jsx-runtime' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.

from primitives.

dimitur2204 commented on June 29, 2024