(OK) with vercel/next.js#13542

if vercel/next.js#13542 is merged, most of the
yarn workspace + typescript config will be picked up automatically,
removing the need for next-transpile-modules

packages/web-app/next.config.js

@@ -1,18 +1,29 @@
 // Tell webpack to compile the "bar" package, necessary if you're using the export statement for example
 // https://www.npmjs.com/package/next-transpile-modules
-const withTM = require("next-transpile-modules")(["bar"]);
+//const withTM = require("next-transpile-modules")(["bar"]);
 
 const TsconfigPathsPlugin = require("tsconfig-paths-webpack-plugin");
 
 const nextConfig = {
   webpack: function (config) {
+    /*
+     Optionnaly, adding the following to modules
+     will resolve modules using relative paths instead of
+     going through `<rootDir>/node_modules`
+    */
+    /*
+    config.resolve.modules = [
+      path.join(__dirname, ".."),
+      ...config.resolve.modules,
+    ];
+    */
     config.resolve.plugins = [
       ...config.resolve.plugins,
       new TsconfigPathsPlugin(),
     ];
-
     return config;
   },
 };
 
-module.exports = withTM(nextConfig);
+//module.exports = withTM(nextConfig);
+module.exports = nextConfig;