Installing a module for a companion that is under development (not through the companion interface)

I understand that this is probably a children’s problem, but I don’t know how to solve it.
I’m trying to test a module for a companion that is currently in development, it’s not available through the companion interface, I just downloaded it from github.

I just downloaded the code from github as a folder
and I placed the module folder along the path
C:\Program Files\Companion_Beta\resources\module-legacy\manifests
Where the companion itself is installed.

When starting the module it gives an error

system: ** Starting Connection from “C:\Program Files\Companion_Beta\resources\module-legacy\manifests\companion-module-limagiran-holyrics-main\main.js” **
system: ** Connection started **
error: node:internal/modules/cjs/loader:1137
throw err;

Error: Cannot find module ‘@companion-module/base’
Require stack:

  • C:\Program Files\Companion_Beta\resources\module-legacy\manifests\companion-module-limagiran-holyrics-main\main.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15)
    at Module._load (node:internal/modules/cjs/loader:975:27)
    at Module.require (node:internal/modules/cjs/loader:1225:19)
    at require (node:internal/modules/helpers:177:18)
    at Object. (C:\Program Files\Companion_Beta\resources\module-legacy\manifests\companion-module-limagiran-holyrics-main\main.js:1:64)
    at Module._compile (node:internal/modules/cjs/loader:1356:14)
    at Module._extensions…js (node:internal/modules/cjs/loader:1414:10)
    at Module.load (node:internal/modules/cjs/loader:1197:32)
    at Module._load (node:internal/modules/cjs/loader:1013:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) {
    code: ‘MODULE_NOT_FOUND’,
    requireStack: [
    ‘C:\Program Files\Companion_Beta\resources\module-legacy\manifests\companion-module-limagiran-holyrics-main\main.js’

Node.js v18.19.1
system: ** Connection stopped **

Tell me what am I doing wrong and how can I fix it?

Open Terminal (Mac) or the Command Line (Windows) and go to the folder that contains the module, and type
See if that fixes the problem.

Might not work though if you don’t have a dev environment set up.
IIWU, I’d contact the dev and ask them to create a dev build that you can download, like I do here.

yeah, it didn’t work…
I guess I’m missing some components to make it work :frowning:

contact the Developer and ask him/her to make you a build.