Error: Cannot find module 'unit-http/loader' about unit HOT 3 CLOSED

Attempt to execute the npm command or add a dependency

npm install unit-http 

from unit.

That executes successfully:

user@debian:~/repos/expressunit$ npm install unit-http 

changed 1 package, and audited 66 packages in 985ms

12 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

package.json

{
  "dependencies": {
    "express": "^4.19.2",
    "unit-http": "^1.32.1"
  },
  "name": "expressunit",
  "version": "1.0.0",
  "main": "app.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "description": ""
}

I attempted a few different combinations on my Debian 12 OS (not the live OS as above, which ws just for a clean repro), all of which still give the same error as shown in my first post, when applying the config:

1. without linking at all:
   1. take back app ownership as user
   2. remove global unit-http install: sudo npm -g uninstall unit-http
   3. rm -rf node_modules package-lock.json
   4. npm install express unit-http
   5. chown app unit:unit
   6. apply config
2. global install, local install, no link:
   1. redo sudo npm install -g --unsafe-perm unit-http
   2. take back app ownership as user
   3. rm -rf node_modules package-lock.json
   4. npm install express unit-http
   5. chown app unit:unit
   6. apply config
3. global install, local install, then link:
   1. with unit-http still available as global dependency
   2. take back app ownership as user
   3. rm -rf node_modules package-lock.json
   4. npm install express unit-http
   5. sudo npm link unit-http
   6. chown app unit:unit
   7. apply config
4. global install, link, then local install:
   1. with unit-http still available as global dependency
   2. take back app ownership as user
   3. sudo npm link unit-http
   4. npm install express unit-http
   5. chown app unit:unit
   6. apply config

from unit.

Check whether the working_directory configured in the unit is the application root directory?
Or enter the container and execute the command node -e 'require('unit-http/loader')'

from unit.