Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: Utils.isRegExp is not a function #552

Open
reeseovine opened this issue Oct 21, 2024 · 1 comment
Open

TypeError: Utils.isRegExp is not a function #552

reeseovine opened this issue Oct 21, 2024 · 1 comment

Comments

@reeseovine
Copy link

reeseovine commented Oct 21, 2024

No matter how I try to run mjolnir, it always seems to fail right away with this error message:

/opt/mjolnir/node_modules/config/lib/config.js:1006
    } else if (Utils.isRegExp(parent)) {
                     ^

TypeError: Utils.isRegExp is not a function
    at _clone (/opt/mjolnir/node_modules/config/lib/config.js:1006:22)
    at Config.cloneDeep (/opt/mjolnir/node_modules/config/lib/config.js:1046:10)
    at /opt/mjolnir/node_modules/config/lib/config.js:1318:32
    at Array.forEach (<anonymous>)
    at util.extendDeep (/opt/mjolnir/node_modules/config/lib/config.js:1293:9)
    at /opt/mjolnir/node_modules/config/lib/config.js:651:12
    at Array.forEach (<anonymous>)
    at util.loadFileConfigs (/opt/mjolnir/node_modules/config/lib/config.js:648:16)
    at new Config (/opt/mjolnir/node_modules/config/lib/config.js:113:27)
    at Object.<anonymous> (/opt/mjolnir/node_modules/config/lib/config.js:1510:31)

Node.js v23.0.0

This is on v1.8.0 as well as main

Invocations I've tried:

  • node lib/index.js --mjolnir-config ./config/production.yaml
  • /usr/bin/node /opt/mjolnir/lib/index.js --mjolnir-config /opt/mjolnir/config/production.yaml
  • yarn run start:dev --mjolnir-config /opt/mjolnir/config/production.yaml

* This is a Debian 12 system. I installed nodejs from apt, then corepack enable for yarn. I followed the self-build guide and there were no errors until trying to run it.

@arjan-s
Copy link

arjan-s commented Oct 31, 2024

Same here on 1.8.3 (the latest release atm). In my case it was caused by upgrading nodejs from (22.10.0-1 -> 23.1.0-1). Downgrading nodejs again fixed the issue (temporarily obviously).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants