Cannot find module react-native-worklets/core

[haadbaig]

Description

I am using react native sdk 53 with nativewind. Everything was working fine till 12 september 2025 (3 days ago). My project was building correctly with npx expi run:ios --device.

Suddenly I started getting the issue cannot find modulereact-native-worklets/plugin. I tried again and again and still got same error. After spending almost 20 hours I figured out that react-native-css-interop causing the issue. It tried to pull react-native-worklets but could not do so. I tried installing worklet library directly still didn't work.

This is the complete error:

ERROR node_modules/react-native-css-interop/.cache/ios.js: [BABEL] /Users/haadbaig/Documents/Work/JamesCoote/t-stop-pro/node_modules/react-native-css-interop/.cache/ios.js: Cannot find module 'react-native-worklets/plugin'
Require stack:

• /Users/haadbaig/Documents/Work/JamesCoote/t-stop-pro/node_modules/@babel/core/lib/config/files/plugins.js
• /Users/haadbaig/Documents/Work/JamesCoote/t-stop-pro/node_modules/@babel/core/lib/config/files/index.js
• /Users/haadbaig/Documents/Work/JamesCoote/t-stop-pro/node_modules/@babel/core/lib/index.js
• /Users/haadbaig/Documents/Work/JamesCoote/t-stop-pro/node_modules/metro-transform-worker/src/index.js
• /Users/haadbaig/Documents/Work/JamesCoote/t-stop-pro/node_modules/react-native-css-interop/dist/metro/transformer.js
• /Users/haadbaig/Documents/Work/JamesCoote/t-stop-pro/node_modules/metro/src/DeltaBundler/Worker.flow.js
• /Users/haadbaig/Documents/Work/JamesCoote/t-stop-pro/node_modules/metro/src/DeltaBundler/Worker.js
• /Users/haadbaig/Documents/Work/JamesCoote/t-stop-pro/node_modules/jest-worker/build/workers/processChild.js

Make sure that all the Babel plugins and presets you are using
are defined as dependencies or devDependencies in your package.json
file. It's possible that the missing plugin is loaded by a preset
you are using that forgot to add the plugin to its dependencies: you
can workaround this problem by explicitly adding the missing package
to your top-level package.json.

Steps to reproduce

1. Setup nativewind. refer to their documentation
2. Try building your project locally

Snack or a link to a repository

https://github.com/haadbaig/tstoppro-frontend

Reanimated version

3.17.4

Worklets version

0.2.0

React Native version

0.79.5

Platforms

iOS

JavaScript runtime

None

Workflow

None

Architecture

None

Build type

No response

Device

No response

Host machine

None

Device model

IPhone 12 pro max

Acknowledgements

Yes

[jcuervas]

I had this issue, it has something to do with latest release. I've downgraded to 3 and it worked again. I think we have to wait to upgrade until this is fixed

[khanhjp1]

please remove 2 package "@react-navigation/drawer": "^7.5.8",
"@react-navigation/native": "^6.1.7",
and re-install with new package
"@react-navigation/drawer": "^7.5.8",
"@react-navigation/native": "^7.1.17",
App work

[ttareq10]

I have been struggling with same issue with React native version 0.75.5, nativewind 4.1.23 and react-native-reanimated : 3.19.0.
I have fixed the issue by adding override rules on the package.json as -

"overrides": { "nativewind": { "react-native-css-interop": "0.1.22" } }

Note : Need to mentioned your project's react-native-css-interop version.

Then Remove and reinstall node and pod as -

On the root folder -

rm -rf node_modules
rm -rf package-lock.json 
npm install 

Go the ios project folder with -> cd ios

rm -rf ios/build
rm -rf ios/Pods
rm -rf ios/Podfile.lock
pod install 

and Finally run from the root project folder -

npx react-native run-ios
Boom!

Hope it will solve your problem too!

I have been struggling with same issue with React native version 0.75.5, nativewind 4.1.23 and react-native-reanimated : 3.19.0. I have fixed the issue by adding override rules on the package.json as -

"overrides": { "nativewind": { "react-native-css-interop": "0.1.22" } }

Note : Need to mentioned your project's react-native-css-interop version.

Then Remove and reinstall node and pod as -

On the root folder -

rm -rf node_modules
rm -rf package-lock.json 
npm install 

Go the ios project folder with -> cd ios

rm -rf ios/build
rm -rf ios/Pods
rm -rf ios/Podfile.lock
pod install 

and Finally run from the root project folder -

npx react-native run-ios Boom!

Hope it will solve your problem too!

Thanks @ttareq10

[tjzel]

Reanimated 3 doesn't work with react-native-worklets installed https://docs.swmansion.com/react-native-reanimated/docs/guides/compatibility#supported-react-native-worklets-versions. However this isn't the root cause of this issue.

Perhaps some Babel preset is including react-native-worklets/plugin when it detects Reanimated but assumes it's Reanimated 4 so it breaks when it's Reanimated 3 without Worklets installed.

[BoavistaLudwig]

I had the same issue. fix: downgrading to nativewind 4.1.23 and adding override rules on the package.json as -

"overrides": { "nativewind": { "react-native-css-interop": "0.1.22" } }

thanks @ttareq10

[r-variichuk]

if u use nativewind, make sure to use version 4.1.23

[haadbaig]

Reanimated 3 doesn't work with react-native-worklets installed https://docs.swmansion.com/react-native-reanimated/docs/guides/compatibility#supported-react-native-worklets-versions. However this isn't the root cause of this issue.

Perhaps some Babel preset is including react-native-worklets/plugin when it detects Reanimated but assumes it's Reanimated 4 so it breaks when it's Reanimated 3 without Worklets installed.

yes react-native-css-interop uses react-native-worklets/plugin. I commented this out and created a patch for it. Its working fine for me and even i was able to get working build for test flight But I personally dont like solutions where we have to patch packages

[Bishoy-Saber]

I had the same issue with react-native v0.79.5, expo v53, nativewind v4.1.23 and react-native-css-interop 0.2.1.
Thanks @haadbaig that solves the error.

[bloms11]

@BoavistaLudwig your fix worked for me too...thanks

[tjzel]

Silencing the warning coming from "react-native-reanimated/plugin" in #8267 will allow for libraries to use it without spamming the users stdout and should allow library authors to fix this issue.