libdragon 11.4.2 → 11.4.4

package/README.md

@@ -222,10 +222,12 @@ npm run libdragon -- update
 
 The root `bench` recipe is for building the code in root `src` folder. This is a quick way of testing your libdragon changes or a sample code built around libdragon, and is called the test bench. This recipe together with `examples` and `tests` recipes will build and install libdragon automatically as necessary. Thus, they will always produce a rom image using the libdragon code in the repository via their make dependencies, which is ideal for experimenting with libdragon itself. 
 
-There are also vscode launch configurations to quickly build the examples, tests and the bench. If you have the `N64_EMU` environment variable set pointing at your favourite emulator ([ares](https://ares-emu.net/) is highly recommended), the launch configurations ending in `(emu)` will kick your emulator with the selected example/code. You can also just hit F5 to launch the selected configuration.
+There are also vscode launch configurations to quickly build and run the examples, tests and the bench. If you have [ares](https://ares-emu.net/) on your `PATH`, the launch configurations ending in `(emu)` will start it automatically. For the examples configuration, you can navigate to the relevant `.c` file and `Run selected example` will start it most of the time. In some cases, the output ROM name may not match the `.c` file and in those cases, you can select the ROM file instead and it should work.
 
 > [!NOTE]
-> This repository also uses [ed64](https://github.com/anacierdem/ed64), so you can use the launch configurations without `(emu)` to run the code if you have an everdrive plugged in and your active configuration will just boot up.
+> This repository also uses [UNFLoader](https://github.com/buu342/N64-UNFLoader), so you can use the launch configurations without `(emu)` to run the code if you have a supported flashcart plugged in and have `UNFLoader` executable on your `PATH`.
+>
+> The special `Debug Test Bench (emu)` configuration will start ares with remote debugging for the test bench if you have `gdb-multiarch` executable on your `PATH`. It should automatically break in your `main` function.
 
 You can clean everything with the `clean` recipe/task (open the command palette and choose `Run Task -> clean`).
 

package/modules/actions/version.js

@@ -1,6 +1,6 @@
 const sea = require('node:sea');
 
-const { log } = require('../helpers');
+const { print } = require('../helpers');
 
 const printVersion = async () => {
   // Version is set during build time. If it is not set, it is set to the
@@ -10,7 +10,7 @@ const printVersion = async () => {
     const { version } = require('../../package.json');
     globalThis.VERSION = version;
   }
-  log(`libdragon-cli v${globalThis.VERSION} ${sea.isSea() ? '(sea)' : ''}`);
+  print(`libdragon-cli v${globalThis.VERSION} ${sea.isSea() ? '(sea)' : ''}`);
 };
 
 module.exports = /** @type {const} */ ({

package/modules/helpers.js

@@ -307,7 +307,10 @@ const dockerExec = /** @type {DockerExec} */ (
         workDirIndex >= 0 ? finalDockerParams[workDirIndex + 1] : undefined;
       return spawnProcess(finalCmdWithParams[0], finalCmdWithParams.slice(1), {
         ...options,
-        spawnOptions: { cwd: workDir, ...options?.spawnOptions },
+        spawnOptions: {
+          cwd: workDir,
+          ...options?.spawnOptions,
+        },
       });
     }
 
@@ -345,7 +348,17 @@ const dockerExec = /** @type {DockerExec} */ (
         libdragonInfo.containerId,
         ...finalCmdWithParams,
       ],
-      options
+      {
+        ...options,
+        spawnOptions: {
+          env: {
+            // Prevent the annoyin docker "What's next?" message. It messes up everything.
+            DOCKER_CLI_HINTS: 'false',
+            ...options?.spawnOptions?.env,
+          },
+          ...options?.spawnOptions,
+        },
+      }
     );
   }
 );

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "libdragon",
-  "version": "11.4.2",
+  "version": "11.4.4",
   "description": "This is a docker wrapper for libdragon",
   "main": "index.js",
   "engines": {
@@ -88,7 +88,7 @@
               "label": "Linux executable"
             },
             {
-              "path": "libdragon-macos-x86_64.tar.gz",
+              "path": "libdragon-macos-arm64.tar.gz",
               "label": "MacOS executable"
             },
             {