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
using config. ...
to initialize a module config variable value in config.js
fails
#2863
Comments
this fails on 2.18 and 2.19 (the folder is 2.17.1 but upgraded to 2.18) |
what part of that config is the culprit? what does the config check script say? |
I don't understand 1st part, I marked the line
config:check finds no issue |
sorry, didnt see that, my bad. do you know when it was the last time this worked? config:check of course finds no issue since this is valid js, it cant do runtime checking of this (which might be a nice feature if it was possible. is it I ask myself?) |
no idea. I need to look at age of module readme why doesn't check use require()? |
readme was last updated 2 years ago. so 2.19-8 2.10-2.11 for sure. but this is the first I've seen of this error. I know the module has been used since then, and there are others. |
do you mean for reading the config js file? |
what is different about config:check usage of config.js vs runtime usage? one works, the other doesn't |
config. ...
to initialize a module config varible value in config.js
fails
config. ...
to initialize a module config varible value in config.js
failsconfig. ...
to initialize a module config variable value in config.js
fails
I digged a bit into this and found that it has something to do with the changes from If I change the content of |
module config
used to work,
fails with this error now
recreate add this module def into config.js
start MM with npm start
were we depending on some lazy evaluation which doesn't exist anymore?
The text was updated successfully, but these errors were encountered: