-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: (0 , _flags.default) is not a function #1183
Comments
It can be a conflict with Please, add a reproducible example, without it I can't say more. |
I have made a repo where the error can be reproduced (hopefully): https://github.com/smooth-organization/jest-error Clone, yarn install and yarn run test-react. I've added two tests in the provided example - one simple and one with react rendering. The simple tests used to break because of the 5.1.3 version of the aria-query package.
I added the resolution field in the package.json file so that the project only uses the 5.0.0 version. With that done the simple test runs fine, but the react rendering one fails:
|
Thanks, I was able to reproduce it. It's hard to understand the reason - it still looks like a conflict. I need time to dig it out. |
Thanks. I've been doing some investigating myself. I have a branch where I use the following resolutions and everything works: "core-js-compat": "3.20.2", I wish I can dig deeper into this but I have a lot of work atm. I'll post updates when I can! |
Right! These are the steps that are needed in order to get the error:
|
Greetings!
I have a react project that runs on yarn with nodeLinker: "pnp" (zero installs), and I'm getting the following error when I try to run tests:
I'm using react 18.2.0, @testing-library/react 13.4.0 and @testing-library/jest-dom 5.16.5. I really can't provide any more details and I understand that this might not be enough for anything and that this might not be related to core-js at all, I'm just wondering has anyone else experienced similar issue? Thanks in advance and I apologize for the scarce information.
The issue is not present when I set the nodeLinker to node_modules, which is when yarn uses the node_modules folder approach to handle packages.
The text was updated successfully, but these errors were encountered: