Hermes bytecode cache invalidation during React Native development-to-production migration

Hermes Bytecode Cache Invalidation During Migration

When migrating a small React Native application to production with Hermes enabled, the transition from development to production builds requires careful handling of the bytecode cache. The Hermes engine compiles JavaScript to platform-specific bytecode (.hbc files), which provides significant bundle size reduction and startup performance improvements.

During development, live reload and Fast Refresh operations can leave native module references in inconsistent states, particularly affecting async storage, network listeners, and other native resources. While production builds disable live reload, the migration process must ensure complete cache invalidation to prevent stale bytecode from being used.

The bytecode cache is platform-specific and not forward-compatible across React Native versions. This creates uncertainty about whether automatic cache clearing mechanisms properly handle all edge cases during the build pipeline transition.

Specific questions:

• Does React Native's build system automatically clear and regenerate Hermes bytecode cache when transitioning from development to production builds?
• What is the recommended approach to verify complete bytecode cache invalidation before production deployment?
• Are there documented lifecycle hooks or configuration options to ensure native module cleanup during development reloads?