Tutorial - Error when click Save at Edit

[CCH4GITHUB]

Edit, Click Save gives rise to this error message

Error: 500 Internal Server Error
Error
at createConstructor (C:\Users\User\AppData\Roaming\npm\node_modules\geddy\lib\response\errors.js:68:34)
at new (C:\Users\User\AppData\Roaming\npm\node_modules\geddy\lib\response\errors.js:79:33)
at Object. (C:\Users\User\AppData\Roaming\npm\node_modules\geddy\lib\response\errors.js:21:10)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)

[ckhatton]

Are you using node "~> 5.12.0"?

[CCH4GITHUB]

Hi Chris Latest LTS Version: v6.9.5 (includes npm 3.10.10)

…

On Sun, Feb 19, 2017 at 6:19 PM, Chris Hatton ***@***.***> wrote: Are you using node "~> 5.12.0"? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#725 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXf65v_DshoeZVJA8Law_DwuFFAPzvBoks5reBcsgaJpZM4L_Hkm> .

[ckhatton]

What's LTS? 😕

The node version cannot be any higher than v5 for Geddy to function. 🐙

[ckhatton]

I get what you mean now, the node version has to be v5. You can use 'nvm' if you want to manage the versions.

[ckhatton]

@CCH4GITHUB Can I close this issue now? 🚪

[mde]

@ckhatton, did we open a ticket for getting Ged working on the newest Nodes?

[ckhatton]

I don't believe one has been created.

Can I possibly have a higher level of access? I would like to go through the issues and label them 'bug', 'feature', etc.

[mde]

Done!

[ckhatton]

Actually, doesn't look like it worked...

[mde]

Look for an invitation to the group in e-mail.

[ckhatton]

I still haven't received the email :( I have checked my spam folder as well.

[mde]

Ugh. Can you look in your GitHub notifications to see if it's there? Maybe your notifications don't go to e-mail?

[mde]

@ckhatton Is this the same error you saw trying to use Ged with the latest Node?

[mde]

Looks like the breakage was caused by nodejs/node#6289, changing the querystring module to use null-proto objects. Fixed in mde/utilities@c906146 Update your deps, and things should work. Let me know if there's more breakage.

[ckhatton]

Thinking about it, I think it was haha. An error would occur when saving a database record - So it does sound the same.

I kinda get the solution haha. Out of interest, how does Geddy link to the utilities repo? Do you have a asset call link to the raw source file in the utilities repo?

I have just tested the Geddy tutorial using Node v6, and it is working fine 😃👍

P.S:
I have noticed the page assets load in slower using Node v6. The background is white for a second, until the grey texture has loaded into the DOM.

[mde]

Geddy just uses the utilities lib as a standard CommonJS require. You can see all the stuff it uses in the package.json.

I haven't noticed any specific speed difference with Node 6, but in production, you probably wouldn't want to be serving the static assets with Node anyhow. You'd front your app with something like Ngnix to serve those.

[ckhatton]

Geddy just uses the utilities lib as a standard CommonJS require.

Oh yeah, of course!