[commit mixup] README: shared-code-entry instructions enhanced

npm-install-subfolders.js

@@ -0,0 +1,48 @@
+const { execSync } = require('child_process');
+const { readdirSync, statSync } = require('fs');
+const { join, resolve } = require('path');
+
+
+const initialDir = process.cwd(); // Store the initial working directory
+
+function findDirectSubfolders(dir) {
+    const subfolders = [];
+    const items = readdirSync(dir);
+
+    items.forEach(item => {
+        const fullPath = join(dir, item);
+        if (statSync(fullPath).isDirectory()) {
+            // Check if the directory contains a package.json file
+            if (readdirSync(fullPath).includes('package.json')) {
+                subfolders.push(fullPath);
+            }
+        }
+    });
+
+    return subfolders;
+}
+
+function installInSubfolders(subfolders) {
+    subfolders.forEach(folder => {
+        try {
+            console.log(`Installing npm packages in ${folder}...`);
+            process.chdir(folder);
+            execSync('npm install', { stdio: 'inherit' });
+        } catch (error) {
+            console.error(`Failed to install in ${folder}: ${error}`);
+            // process.exit(1);
+        } finally {
+            process.chdir(initialDir); // Always return to the initial directory
+        }
+    });
+}
+
+const rootDir = process.argv.length>2 ? resolve(process.argv[2]) : resolve('./widgets'); // Ensure rootDir is an absolute path
+console.log(`Searching for widget folders in rootDir '${rootDir}'`);
+
+const subfolders = findDirectSubfolders(rootDir);
+console.log('Widget folders found:', subfolders);
+
+installInSubfolders(subfolders);
+
+console.log('npm install completed in all direct subfolders.');

package.json

@@ -0,0 +1,10 @@
+{
+  "name": "exb-workshop",
+  "version": "1.1.0",
+  "description": "themes + widgets in root, own package.json",
+  "main": "",
+  "scripts": {
+    "install-subfolders": "node npm-install-subfolders.js"
+  },
+  "author": ""
+}

widgets/share-code-widgets/share-code-entry/README.md

@@ -28,4 +28,22 @@ To support i18n, create a `translations` folder within the `shared-code` folder,
 * At last, you can import the shared code like using the standard ES6 imports, like this:
 ```typescript
 import { sampleFunction } from 'widgets/shared-code/entry1'
-```
+```
+
+## Path resolution of ``shared-code``
+
+By default, the ``paths.widgets`` array in your ``tsconfig.json`` only contains a reference to ``"./your-extensions/widgets/*"``. To enable the TS compiler to find your shared code when importing it in your widget and business code, enhance the array with the folder names of the repositories with ``/widgets/`` postfix:
+
+```
+"paths": {
+  [...]
+  "widgets/*": [
+    "./your-extensions/widgets/*",
+    "./<your_repository>/widgets/*"
+  ]
+}
+```
+
+## Using shared code in multiple web-extension-repos
+
+To ensure that no entries are overwritten, the central ``ts`` file with the collected exports should be named individually. For example, instead of ``entry1.ts``, you would be using ``entry_<project_name>.ts`` in your repository.