Skip to main content

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 your package.json dependencies manually:
package.json
Then install the required peer dependencies:
The first installation attempt will fail because you are not yet authorized. This is expected - continue with the authentication step below.
Check the Compatibility page for supported React Native, Expo, and Nitro Modules versions.

Authenticate with GitHub

Run the CLI to authenticate:
You’ll see the following menu:
Select “Login with Github”:
  1. A browser tab will automatically open
  2. Sign in with your GitHub account
  3. Authorize the application
  4. Wait for the success message: “You can close this tab and return to the terminal.”
After successful authentication, you’ll see:
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”:
The CLI will automatically fetch and install the Uniwind Pro package from the CDN.
The installation process automatically handles version compatibility, ensuring you get the correct Pro version for your CLI.

Configure Babel

Add the react-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.
If you’re already using Reanimated, you may already have react-native-reanimated/worklets in your config.

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 blocks postinstall scripts by default. To allow the Uniwind postinstall script, add to your package.json:
package.json
If postinstall scripts don’t run, Uniwind Pro may fail to initialize correctly. You’ll see errors about missing native modules or configuration.

Rebuild Your App

After installation, rebuild your native app:
Then run your app:
A native rebuild is required for Uniwind Pro to work correctly. Simply restarting Metro is not enough. Uniwind Pro doesn’t work with Expo Go.

Verify Installation

After rebuilding, verify that Uniwind Pro is working:
  1. Check that your app starts without errors
  2. Try using a Pro-only feature like Theme Transitions
  3. Verify the CLI shows your license status:
You should see your username and session validity.
You can verify that the CLI stub was replaced with the actual Uniwind Pro code by checking if node_modules/uniwind contains native modules (.cpp, .mm files) instead of just the CLI placeholder.

Troubleshooting

Try running the CLI with elevated permissions or check that your package manager has write access to node_modules.
See the Whitelisting Postinstall Scripts section above. Most issues are caused by package managers blocking scripts.
Ensure you’ve rebuilt the native app after installation. Delete ios/build and android/build folders, then rebuild.
Run uniwind-pro again and select “Login with Github” to re-authenticate. Sessions are valid for 180 days.
Each license type has monthly download limits. Check your dashboard for current usage. Limits reset at the start of each month.

Still having issues?

Open an issue on GitHub and we’ll help you out. Pro users receive priority support.