Skip to content
Native Animation
Native Animation / Base
Base docs Native Animation Base Installation
Connect the MCP →

Native Animation Base Installation

Install free MIT Base components in your Expo project with the CLI, MCP, or a source download. Follow the setup guide. No account, email, or card required.

With an agent

Connect the MCP and ask it to set up Base for your existing project. It reads the component docs and selects a compatible source revision.

  1. Choose your project

    Start inside an Expo project. Check the compatibility table on the component page against your project’s Expo SDK. Keep support modules and components on the same SDK revision. The catalog baseline is Expo SDK 58 and Expo SDK 57; the component’s live compatibility table is authoritative.

  2. Add a component

    npx nativeanimation add base-button

    No login is needed for Base. The CLI copies editable source and its transitive family dependencies, including base-theme when required. It installs missing native packages with Expo’s SDK-compatible installer.

    The default destination is src/components when your project has a src folder, or components otherwise. Use --path to choose another directory. Keep helpers outside the route directory.

  3. Read the delivered README

    Use the import path returned by the installer and the component’s documented props. Read its README before connecting values and callbacks. Load the font families expected by the theme once at the app root. Preserve your existing providers, splash handling, and navigator configuration.

    For gestures, follow the README’s root-container setup. Adding a native package that is not bundled with Expo Go requires a development build. See compatibility.

Manual installation

Open a published component and expand Source code. Download the .tar.gz archive without an account and extract it. It includes the complete family dependency closure for the selected SDK, plus the license files. Keep the folders next to each other so relative imports resolve, then install the packages listed in the README.

The public registry item at /r/base-button.json describes that component’s files and dependencies. It is metadata for tooling; downloading one JSON file does not install its dependencies. The CLI or MCP is the easiest way to get the complete dependency closure.

Verify the screen

Connect real state and callbacks. Check light and dark modes, large text, screen-reader labels, reduced motion, keyboard behavior, and the native platforms you ship.

Theming · Troubleshooting