fix(example): resolve react/react-native from the example app (#6)

In this library+example layout, npm auto-installs the library's peerDependencies
(expo, react, react-native) at their latest versions into the repo-root
node_modules. The example's Metro watches the monorepo root, so codegen could pull
the root's newer react-native and fail ("Unable to determine event arguments" in
VirtualViewNativeComponent). Pin the react/react-native singletons to the example's
own node_modules and block the root copies.

Author: pablogdcr

example/metro.config.js

@@ -15,4 +15,20 @@ config.resolver.nodeModulesPaths = [
   path.resolve(monorepoRoot, 'node_modules'),
 ];
 
+// The monorepo root also carries its own (newer) react / react-native, pulled in
+// by npm auto-installing the library's peerDependencies. Pin the singletons to the
+// example's copies so Metro and React Native codegen never mix versions — mixing
+// breaks native component codegen (e.g. "Unable to determine event arguments" in
+// VirtualViewNativeComponent).
+config.resolver.extraNodeModules = {
+  react: path.resolve(projectRoot, 'node_modules/react'),
+  'react-native': path.resolve(projectRoot, 'node_modules/react-native'),
+};
+
+const escapeForRegExp = (p) => p.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
+config.resolver.blockList = [
+  new RegExp(`^${escapeForRegExp(path.resolve(monorepoRoot, 'node_modules/react-native'))}/.*`),
+  new RegExp(`^${escapeForRegExp(path.resolve(monorepoRoot, 'node_modules/react'))}/.*`),
+];
+
 module.exports = config;