chore(compartment-mapper): reformat

Author: boneskull

packages/compartment-mapper/src/hooks.js

@@ -248,7 +248,7 @@ export const makeHookExecutor = (
 
     // Direct hook (e.g., "moduleSource", "packageDescriptor")
     const hookValue = effectiveConfig[name];
-    
+
     if (hookValue === undefined) {
       return undefined;
     }

packages/compartment-mapper/src/types/external.ts

@@ -622,7 +622,7 @@ export type FileUrlString = `file://${string}`;
  * Options provided to all Compartment Map Transforms.
  */
 export type CompartmentMapTransformOptions = Required<LogOptions> &
-  PolicyOption
+  PolicyOption;
 
 /**
  * Public API provided to a {@link CompartmentMapTransformFn} as the

packages/compartment-mapper/test/fixtures-dynamic-ancestor/README.md

@@ -10,7 +10,7 @@ sequenceDiagram
   participant pantspack
   participant pantspack-folder-runner
   participant jorts-folder
-  
+
   activate app
   app->>+pantspack: run pantspack
   deactivate app
@@ -28,9 +28,9 @@ sequenceDiagram
 
 ```
 
-The main "app" is `webpackish-app`, which contains a [`pantspack.config.js`](./node_modules/webpackish-app/pantspack.config.js) file. This file specifies the _name_ of a "folder", which is `jorts-folder`. `jorts-folder`  _is not_ loaded directly by `pantspack.config.js`.
+The main "app" is `webpackish-app`, which contains a [`pantspack.config.js`](./node_modules/webpackish-app/pantspack.config.js) file. This file specifies the _name_ of a "folder", which is `jorts-folder`. `jorts-folder` _is not_ loaded directly by `pantspack.config.js`.
 
-`webpackish-app` uses `pantspack` to "build" itself.  Its `build` script:
+`webpackish-app` uses `pantspack` to "build" itself. Its `build` script:
 
 ```sh
 node ../pantspack/pantspack.js --config pantspack.config.js

packages/compartment-mapper/test/fixtures-implicit-reexport/package.json

@@ -6,4 +6,3 @@
     "preinstall": "echo DO NOT INSTALL TEST FIXTURES; exit -1"
   }
 }
-

packages/compartment-mapper/test/fixtures-optional-peer-dependencies/README.md

@@ -1,9 +1,9 @@
 This fixture is for testing the behavior of `mapNodeModules()` when a package has no declared `peerDependencies` _but_ has a `peerDependenciesMeta` field listing an _optional_ dependency.
 
-The _intent_ of this configuration is to declare _optional_ peer dependencies.  
+The _intent_ of this configuration is to declare _optional_ peer dependencies.
 
 `npm@7+` requires all dependencies mentioned in `peerDependenciesMeta` must to be declared in `peerDependencies`. This enables automatic installation of the peer dependencies (which is then allowed to fail).
 
-Prior to `npm@7`, there was no way to declare a peer dependency as optional, leading packages to _omit_ optional `peerDependencies` from `package.json`.  
+Prior to `npm@7`, there was no way to declare a peer dependency as optional, leading packages to _omit_ optional `peerDependencies` from `package.json`.
 
 I do not know if `yarn` or `pnpm` (any version) do anything with a lone `peerDependenciesMeta` field. Assuming they don't, `peerDependenciesMeta` w/o a `peerDependencies` is little more than a _hint_ to a human reader.

packages/compartment-mapper/test/make-import-hook-maker.hooks.test.js

@@ -34,9 +34,9 @@ const testFixture = {
 
 /**
  * AVA macro for testing moduleSource hook with different loader functions
- * 
+ *
  * This could be more narrowly-typed, but it's a test.
- * 
+ *
  * @param {ExecutionContext} t
  * @param {object} options
  * @param {Function} options.loaderFn - The function to call (captureFromMap, loadFromMap, or loadLocation)

packages/compartment-mapper/test/policy.test.js

@@ -114,7 +114,6 @@ const anyExpectations = {
   }),
 };
 
-
 const powerlessCarolExpectations = {
   namespace: moduleify({
     ...defaultExpectations.namespace,
@@ -208,7 +207,6 @@ scaffold(
         t.snapshot(sanitizePaths(error.message), 'location case error message');
       }
       // see the snapshot for the error hint in the message
-      
     },
     addGlobals: globals,
     policy: {