Downloaded the new beta today. Saw that it had fixed an issue i was having with using parameters in a custom query, but now i can not get ANY query to run (even a brand new simple select all)
I keep getting this error message when i output to browser:
“message”:“settings is not defined”,“stack”:"ReferenceError: settings is not defined\n at App.define…
So far I have created a new folder, a new SC file and even created a new DB connection. All to no avail.
Further to this. I have now created a brand new project, installed node from scratch etc and tried again. Same result. Full error message here:
{“message”:“settings is not defined”,“stack”:“ReferenceError: settings is not defined\n at App.define (C:\Switchley\nodeJS\test\lib\core\app.js:143:35)\n at C:\Switchley\nodeJS\test\lib\core\middleware.js:12:40\n at Layer.handle [as handle_request] (C:\Switchley\nodeJS\test\node_modules\express\lib\router\layer.js:95:5)\n at next (C:\Switchley\nodeJS\test\node_modules\express\lib\router\route.js:137:13)\n at next (C:\Switchley\nodeJS\test\node_modules\express\lib\router\route.js:131:14)\n at next (C:\Switchley\nodeJS\test\node_modules\express\lib\router\route.js:131:14)\n at next (C:\Switchley\nodeJS\test\node_modules\express\lib\router\route.js:131:14)\n at next (C:\Switchley\nodeJS\test\node_modules\express\lib\router\route.js:131:14)\n at next (C:\Switchley\nodeJS\test\node_modules\express\lib\router\route.js:131:14)\n at next (C:\Switchley\nodeJS\test\node_modules\express\lib\router\route.js:131:14)”}
We will release an update as soon as possible, to fix it temporary is to edit the file lib/core/app.js line 143: clone(settings) should become clone(cfg.settings).
Problem is only in node, not in other environments. Please note that node is currently beta and code changes a lot at the moment.
stack: “TypeError: fields is not iterable at Object.validateFields (F:\webs\findmystudentdigs\lib\validator\index.js:41:27) at Object.init (F:\webs\findmystudentdigs\lib\validator\index.js:6:20) at App.define (F:\webs\findmystudentdigs\lib\core\app.js:152:29) at F:\webs\findmystudentdigs\lib\core\middleware.js:12:40 at Layer.handle [as handle_request] (F:\webs\findmystudentdigs\node_modules\express\lib\router\layer.js:95:5) at next (F:\webs\findmystudentdigs\node_modules\express\lib\router\route.js:137:13) at next (F:\webs\findmystudentdigs\node_modules\express\lib\router\route.js:131:14) at next (F:\webs\findmystudentdigs\node_modules\express\lib\router\route.js:131:14) at next (F:\webs\findmystudentdigs\node_modules\express\lib\router\route.js:131:14) at next (F:\webs\findmystudentdigs\node_modules\express\lib\router\route.js:131:14)”
I am still running my core projects in 2.9.1 only using 3 beta for silly throw away tests so I can learn a little of the Node side and report the bugs.
I would assume most people are or should be doing the same.
Doing same, between projects downtime to play with node also. But it is not good when my toys are broken. There are a lot of issues with the beta presently which would scare me off using it in any production situation