Using Hermes Engine
Hermes is a JavaScript engine optimized for React Native. By compiling JavaScript into bytecode ahead of time, Hermes can improve your app start-up time. The binary size of Hermes is also smaller than other JavaScript engines, such as JavaScriptCore (JSC). It also uses less memory at runtime, which is particularly valuable on lower-end Android devices.
To get started, open your app.json and add jsEngine field:
{
"expo": {
"jsEngine": "hermes"
}
}
Now you can build an APK or AAB through eas build and your app will run with Hermes instead of JavaScriptCore.
To get started, open your app.json and add jsEngine field:
{
"expo": {
"jsEngine": "hermes"
}
}
Now you can build your app through eas build and your app will run with Hermes instead of JavaScriptCore.
Are you using an M1 Mac?
When using Hermes for iOS, you may encounter the following error when building for the simulator:
❌
ld: building for iOS Simulator, but linking in dylib built for iOS, file '/path/to/projectName/ios/Pods/hermes-engine/destroot/Library/Frameworks/iphoneos/hermes.framework/hermes' for architecture arm64
--- a/ios/Podfile
+++ b/ios/Podfile
@@ -25,6 +25,22 @@ target 'HelloWorld' do
post_install do |installer|
react_native_post_install(installer)
+ # Workaround simulator build error for hermes with react-native 0.64 on mac m1 devices
+ arm_value = `/usr/sbin/sysctl -n hw.optional.arm64 2>&1`.to_i
+ has_hermes = has_pod(installer, 'hermes-engine')
+ if arm_value == 1 && has_hermes
+ projects = installer.aggregate_targets
+ .map{ |t| t.user_project }
+ .uniq{ |p| p.path }
+ .push(installer.pods_project)
+ projects.each do |project|
+ project.build_configurations.each do |config|
+ config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] + ' arm64'
+ end
+ project.save()
+ end
+ end
+
# Workaround `Cycle inside FBReactNativeSpec` error for react-native 0.64
# Reference: https://github.com/software-mansion/react-native-screens/issues/842#issuecomment-812543933
installer.pods_project.targets.each do |target|
Reinstall Pods and clean Xcode build cache:
Terminal
→ npx pod-install
→ xcodebuild clean -workspace ios/{projectName}.xcworkspace -scheme {projectName}
You may want to use Hermes on one platform and JSC on another. One way to do this is to set the "jsEngine" to "hermes" at the top level and then override it with "jsc" under the "ios" key. You may alternatively prefer to explicitly set "hermes" on just the "android" key in this case.
{
"expo": {
"jsEngine": "hermes",
"ios": {
"jsEngine": "jsc"
}
}
}
Publishing updates with expo publish and expo export will generate Hermes bytecode bundles and their source maps.
Please note that the Hermes bytecode format may change between different versions of
hermes-engine — an update produced for a specific version of Hermes will not run on a different version of Hermes. Updating the Hermes version can be thought of in the same way as updating any other native module, and so if you update the
hermes-engine version you should also update the
runtimeVersion in
app.json. If you don't do this, your app may crash on launch because the update may be loaded by an existing binary that uses an older version of
hermes-engine that is incompatible with the updated bytecode format. See
"Update Compatibility" for more information.
To debug JavaScript code running with Hermes, you can start your project with expo start then press j to open the JavaScript inspector in Google Chrome or Microsoft Edge. This is only supported for debug builds.
Alternatively, you can use the JavaScript inspector from the following tools:
💡
Development builds built with
expo-dev-client simplify this process by integrating directly with the JavaScript inspector in Hermes.
The classic build system
isn't flexible enough to support using Hermes for some apps and not for others. You will need to use the new build system,
EAS Build, to use Hermes in your standalone apps.