react-tinder-card: Module not found: Package path ./unstable-native-dependencies is not exported from package

After upgrading to react-tinder-card both v1.6.0 and v1.6.1 with @react-spring/web @9.5.5 I’m experiencing this error after running npm run build

./node_modules/react-panresponder-web/dist/panresponder.js
Module not found: Package path ./unstable-native-dependencies is not exported from package C:\Users\xxx\xxx\Documents\GitHub\xxx\node_modules\react-dom (see exports field in C:\Users\xxx\xxx\Documents\GitHub\xxx\node_modules\react-dom\package.json)

package.json "dependencies": { "next": "^12.3.1", "react": "^18.0.0", "react-dom": "18.0.0", "react-tinder-card": "^1.6.1" },

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 4
Comments: 20 (4 by maintainers)

Most upvoted comments

Also ran into the same issue. It didn’t work on 1.6.1 but it works find when I downgrade to 1.5.4

I’m on: next 12.3.1, react 18.2.0, @react-spring/web 9.5.5

sipec on Oct 27, 2022

@f00d4tehg0dz @CodeOne45 @strangecarr @Develoopment @aseprahman04 @sipec @BotJB @mattg66 This has been fixed in PR https://github.com/3DJakob/react-tinder-card/pull/124 and released in v1.6.2 🎉

Please run npm install react-tinder-card@1.6.2 to resolve the issue.

3DJakob on Nov 7, 2022

I’m well aware of this issue and working on a fix! For now, if you experience this issue please use version 1.5.4.

npm install react-tinder-card@1.5.4

I will post in this thread once I release the new version which fixes this issue.

3DJakob on Nov 3, 2022

Same issue here

mattg66 on Nov 3, 2022

yep same with me, I updated to 1.6.1 on an existing project and getting the same error

strangecarr on Oct 25, 2022

Hey @CodeOne45 I created a new project from scratch and haven’t had an issue. I suspect something else is going on with my existing project. I’ll leave this ticket open to provide any insights once I finish analyzing

ninja edit after placing the card component in the new project, it fails. Digging further into this the react-panresponder-web package is causing the issue. It was raised here: https://github.com/arqex/react-panresponder-web/issues/1 So unless @3DJakob uses a different package, we may just need to revert to an older version.

f00d4tehg0dz on Oct 25, 2022