Packages

IC Reactor ships as a small set of focused packages. Some are runtime libraries you install in applications, while others are tooling packages used during code generation and local development.

Tip

Most frontend apps start with @ic-reactor/react. Add @ic-reactor/candid when you need runtime Candid discovery, and reach for the tooling packages when you want generated code.

Runtime Packages

@ic-reactor/reactReact-first package with hook factories, auth hooks, reactor hooks, and query helpers.

@ic-reactor/coreFramework-agnostic runtime primitives such as ClientManager, Reactor, and DisplayReactor.

@ic-reactor/candidDynamic Candid fetching, runtime method registration, and metadata-driven form generation.

@ic-reactor/parserWASM-based Candid parser used for local compilation and advanced tooling.

Tooling Packages

@ic-reactor/cliCommand-line generator for declarations and ready-to-use reactor hook files.

@ic-reactor/vite-pluginVite integration for automatic code generation, environment injection, and hot reload.

@ic-reactor/codegenShared low-level pipeline used internally by the CLI and Vite plugin.

How They Fit Together

• @ic-reactor/react depends on @ic-reactor/core and re-exports the runtime classes.
• @ic-reactor/candid builds on @ic-reactor/core and can optionally use @ic-reactor/parser for local Candid compilation.
• @ic-reactor/cli and @ic-reactor/vite-plugin both use @ic-reactor/codegen under the hood.
• The tooling packages help you generate declarations and hooks, while the runtime packages execute queries, mutations, auth flows, and dynamic canister calls.