Axonpack

Introduction

What Axonpack is, how these docs are organised, and where to start.

Axonpack makes free, open-source foundation libraries for React Native and Expo apps, and Axon Shaft, a product with its own site. Each library is small, focused and dependency-light. You drop one into an app you already have, rather than adopting a framework.

Every package is published independently, versioned independently, and documented independently. There is no axonpack meta-package to install. Only @axonpack/expo-devtools brings others with it, @axonpack/react-pretty-print and @axonpack/react-native-devtools-tab, as its dependencies.

Every package is MIT licensed and developed in the open at github.com/axonpack/axonpack.

The packages

These docs cover what is published, and nothing else. A page describing something you cannot install would only make you guess which half of this site is real.

Products

Axon Shaft has its own site, and its docs live there rather than here.

How these docs are organised

One folder per package. The sidebar lists them below this page, and picking one puts you in that package's documentation and nothing else. A package's guides, its reference and its screenshots all live under its own name, so nothing here is shared between two libraries by accident.

Inside a package, the shape is always the same:

SectionWhat is in it
Get startedInstall it and wire it up. Read in order the first time.
GuidesOne page per thing it does, written as prose with the limits stated.
ReferenceExhaustive: every control, field, option and exported type. Read by lookup.

Start here

Several packages in one app

Each package's installation page is complete on its own. When an app takes several of them, a few things are shared:

  • Check the requirements once, against the strictest package you are adding, then install them all in one npx expo install with each package's peers.

  • @axonpack/expo-devtools and @axonpack/react-native-devtools-tab both wrap metro.config.js. withDevtools is the same wrap as withReactNativeDevtoolsTab and serves your own tabs too, so use one of them, not both.

  • Every provider and prompt is mounted once, in the root component, one inside the other:

    <PreviewProvider config={previewConfig}>
      <DevtoolsProvider config={{ enabled: __DEV__ }}>
        {/* the app */}
        <UpdatePrompt />
      </DevtoolsProvider>
    </PreviewProvider>
  • Add @axonpack/preview last. It needs a native build for its config plugin, and that one build also links the optional native modules of @axonpack/expo-devtools and @axonpack/in-app-updates.

  • iOS 27 needs Expo SDK 58 or later. After moving to it, regenerate the iOS project with npx expo prebuild --clean -p ios, since a stale ios/ folder crashes at launch.

For AI agents

One agent skill teaches your coding agent to set up and use every package. It reads these docs, so it always matches the latest release. The agent guide is the page it follows, and any agent can read it without the skill. @axonpack/expo-devtools also lets an agent read the running app from a terminal.

On this page