react-native-monorepo-config 0.3.0 → 0.3.2

package/README.md

@@ -63,8 +63,8 @@ module.exports = {
   resolver: {
     ...monoRepoConfig.resolver,
 
-    assetExts: resolver.assetExts.filter((ext) => ext !== 'svg'),
-    sourceExts: [...resolver.sourceExts, 'svg'],
+    assetExts: monoRepoConfig.resolver.assetExts.filter((ext) => ext !== 'svg'),
+    sourceExts: [...monoRepoConfig.resolver.sourceExts, 'svg'],
   },
 };
 ```
@@ -106,12 +106,12 @@ This configuration will setup a few things:
   };
   ```
 
-- Block packages defined in `peerDependencies` of other packages in the monorepo to avoid duplicate versions from being loaded. They must be added under `dependencies` or `devDependencies` in the app's `package.json`.
+- Block packages defined in `peerDependencies` of other packages in the monorepo to avoid duplicate versions from being loaded. They must be added under `dependencies` or `devDependencies` in the app's `package.json` to be resolved correctly.
 
   Loading duplicate versions of some packages such as `react` can cause issues. So this way multiple versions are not loaded. Make sure to specify `peerDependencies` for your packages appropriately.
 
 - If the packages defined in `peerDependencies` have been hoisted to the monorepo root, point Metro to them so they can be found.
-- Configure Metro's resolve to prioritize `package.json#source` or the `source` condition in `package.json#exports` so that the app can import source code directly from other packages in the monorepo.
+- Configure Metro's resolver to prioritize `package.json#source` or the `source` condition in `package.json#exports` so that the app can import source code directly from other packages in the monorepo.
 
   To utilize this, make sure to add the `source` field to the `package.json` of the packages you want to import from, e.g.:
 

package/index.js

@@ -10,6 +10,7 @@ import path from 'node:path';
  * @param {import('metro-config').MetroConfig} baseConfig Base Metro config to extend.
  * @param {string} options.root Root directory path of the monorepo.
  * @param {string} options.dirname Directory path of the current package.
+ * @param {Object} [options.workspaces] Optional list of workspace patterns. By default, `workspaces` field in the `package.json` at root is used.
  *
  * @returns {import('metro-config').MetroConfig}
  */
@@ -135,16 +136,10 @@ export function withMetroConfig(baseConfig, { root, dirname, workspaces }) {
 
   // We need to exclude the peerDependencies we've collected in packages' node_modules
   // Otherwise duplicate versions of the same package will be loaded
-  const blockList = new RegExp(
-    '(' +
-      Object.values(packages)
-        .flatMap((dir) =>
-          peers.map(
-            (m) => `^${escape(path.join(dir, 'node_modules', m))}\\/.*$`
-          )
-        )
-        .join('|') +
-      ')$'
+  const blockList = Object.values(packages).flatMap((dir) =>
+    peers.map(
+      (m) => new RegExp(`^${escape(path.join(dir, 'node_modules', m))}[\/\\\\]`)
+    )
   );
 
   // When we import a package from the monorepo, metro may not be able to find the deps in blockList

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-native-monorepo-config",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "Configure Metro for a React Native app in a monorepo",
   "repository": "https://github.com/satya164/react-native-monorepo-config",
   "author": "Satyajit Sahoo <satyajit.happy@gmail.com> (https://github.com/satya164/)",