Prerequisites
Before installing Uniwind Pro, ensure you have an active Uniwind Pro license.New to Uniwind?
If you’re starting from scratch, follow the Quickstart guide first to set up Tailwind, Metro, and your project structure.
Install Dependencies
Add Uniwind Pro to yourpackage.json dependencies manually:
package.json
- bun
- npm
- yarn
- pnpm
Uniwind Pro 1.8.1 requires
react-native-nitro-modules >= 0.37.1, react-native-reanimated >= 4.0.0, and react-native-worklets >= 0.6.0. Check the Compatibility page for supported React Native, Expo, and Nitro Modules versions.Authenticate with GitHub
Run the CLI to authenticate:- bun
- npm
- A browser tab will automatically open
- Sign in with your GitHub account
- Authorize the application
- Wait for the success message: “You can close this tab and return to the terminal.”
Your authentication session is valid for 180 days. After expiration, you’ll need to re-authenticate.
Install Uniwind Pro Package
From the CLI menu, select “Install Uniwind Pro”:Configure Babel
Add thereact-native-worklets/plugin to your babel.config.js:
babel.config.js
The
react-native-worklets/plugin must be listed in the plugins array to work correctly.Whitelisting Postinstall Scripts
Some package managers block postinstall scripts by default for security reasons. If the Uniwind Pro installation fails or the package doesn’t work correctly, you may need to whitelist the postinstall script.- bun
- yarn (v2+)
- pnpm
- npm
Bun blocks postinstall scripts by default. To allow the Uniwind postinstall script, add to your
package.json:package.json
Rebuild Your App
After installation, rebuild your native app:- Expo
- Bare React Native
Verify Installation
After rebuilding, verify that Uniwind Pro is working:- Check that your app starts without errors
- Try using a Pro-only feature like Theme Transitions
- Verify the CLI shows your license status:
- bun
- npm
Troubleshooting
Installation fails with permission errors
Installation fails with permission errors
Try running the CLI with elevated permissions or check that your package manager has write access to
node_modules.Postinstall script doesn't run
Postinstall script doesn't run
See the Whitelisting Postinstall Scripts section above. Most issues are caused by package managers blocking scripts.
Native module not found errors
Native module not found errors
Ensure you’ve rebuilt the native app after installation. Delete
ios/build and android/build folders, then rebuild.Authentication expired
Authentication expired
Run
uniwind-pro again and select “Login with Github” to re-authenticate. Sessions are valid for 180 days.Download limit reached
Download limit reached
Each license type has monthly download limits. Check your dashboard for current usage. Limits reset at the start of each month.
Unable to resolve "uniwind"
Unable to resolve "uniwind"
Metro can’t find the package entry when it doesn’t use the
exports field of package.json (for example, with unstable_enablePackageExports disabled). Uniwind Pro 1.8.0 adds main and react-native fallback fields. Upgrade to 1.8.0.Metro uses the public uniwind package instead of Pro
Metro uses the public uniwind package instead of Pro
When Pro is installed under an alias (
"uniwind": "npm:uniwind-pro") and Expo autolinking module resolution is enabled, Metro could resolve a hoisted copy of the public uniwind package instead of Pro. Upgrade to 1.8.0, which always resolves uniwind to your app’s copy.Random Missing closing } at @theme errors in CI
Random Missing closing } at @theme errors in CI
Metro workers could read the generated
uniwind.css while another worker was still writing it, which mostly shows up on fresh installs in CI. Uniwind Pro 1.8.0 writes its generated files atomically. Upgrade to 1.8.0.Still having issues?
Open an issue on GitHub and we’ll help you out. Pro users receive priority support.