Stone.js API
    Preparing search index...

    Builds a native application, by asking Expo to.

    Deliberately thin. Expo and Metro own native bundling: they know about Hermes, about the per-platform resolution, about the native projects and about the dev client, and there is nothing to gain from a second opinion on any of it. What this adds is the one thing Expo cannot do, which is collecting your application's modules, and a single vocabulary: stone dev native alongside stone dev, so nobody has to remember which tool owns which platform.

    Anything Expo does better is left to Expo, and left visible: the commands below run in the foreground with their output untouched.

    Implements

    • StoneBuilder
    Index
    • Create the builder.

      Parameters

      • context: ConsoleContext

        The console context.

      Returns NativeBuilder

    • Export the JavaScript bundle.

      This is what a native build means without leaving Node: the bundle Metro produces, for every platform asked for. Producing an installable application is expo run:ios, expo run:android or an EAS build, which need a native toolchain, and wrapping them would only put a thinner command in front of a better one.

      Parameters

      • event: IncomingEvent

        The incoming event.

      Returns Promise<void>

    • Start the development server.

      Parameters

      • event: IncomingEvent

        The incoming event.

      Returns Promise<void>