Re.Pack Documentation

Re.Pack is a modern toolkit that wraps Rspack and webpack to enable them to work seamlessly with React Native applications. It is designed as a drop-in replacement for Metro, aiming to minimize configuration changes while providing enhanced bundling capabilities.

The toolkit provides:

• React Native-specific plugins and loaders: Handles platform-specific files and assets.
• Integrated development server: Includes Hot Module Replacement (HMR), React Refresh, and debugging support via React Native Devtools.
• Runtime modules: Includes ScriptManager for advanced features like code splitting and Module Federation.

Re.Pack's API is organized into three main categories based on where they are used in your workflow:

1. Bundling and Development Configuration (@callstack/repack): Use these APIs to configure your build process. This includes Webpack plugins, utilities, and CLI commands.
2. Client-side Application APIs (@callstack/repack/client): Use these APIs directly inside your application code. A primary example is the ScriptManager.
3. Development Server (@callstack/repack-dev-server): A bundler-agnostic development server. Note that this is primarily intended for users integrating bundlers other than Webpack; if you are using Webpack, this API is likely not required.

Re.Pack API documentation is organized into three main categories based on your integration needs:

1. Bundling and Development Configuration: Use @callstack/repack for Webpack plugins, utilities, and commands used to configure the bundling or development processes.
2. Application-level (Client) APIs: Use @callstack/repack/client for APIs intended to be used inside your application code, such as the ScriptManager.
3. Development Server: Use @callstack/repack-dev-server if you are using a bundler other than Webpack. If you are using Webpack, this API is generally not required.

Re.Pack 5's dev server supports both Rspack and webpack and includes the following development features:

• Hot Module Reloading: Instantly reflects code changes in the app.
• Source Maps: Enables proper debugging with source code mapping.
• Multiple Platforms: Supports both iOS and Android development.
• Development Tools: Integrated with React Native DevTools.

Re.Pack's API documentation is organized into two primary categories based on where the code is executed:

1. React Native API: Documentation for client-facing APIs that run inside your application code (e.g., ChunkManager).
2. Node API: Documentation for APIs used during the bundling or development process, such as Webpack plugins, utilities, and CLI commands.

The @callstack/repack package provides a suite of tools for bundling and serving React Native applications using Webpack. The API is organized into several categories:

• Namespaces: Core logic for Federated modules and plugins management.
• Webpack Plugin Classes: The primary entry point for integrating Repack into a Webpack configuration is the RepackPlugin.
• CLI command Functions: Programmatic access to the CLI commands bundle and start.
• Interfaces & Types: Configuration schemas for the plugin (RepackPluginConfig), dev server (DevServerOptions), and various arguments used during bundling or starting the dev server.
• Webpack Utilities: Helper functions for resolving paths, managing assets, and configuring Webpack environments.

The Federated namespace provides runtime utilities for managing Module Federation. It includes tools for resolving module URLs and dynamically importing modules at runtime. Key components include:

• createURLResolver: A function to create a custom URL resolver for locating federated modules.
• importModule: A function to dynamically import a module using the federated runtime.
• URLResolverConfig: An interface for configuring the URL resolver.
• URLResolver: A type alias representing the resolver function.