Can't start NodeBB on 0.5.1

[esiao]

Hello I have a problem I can't get NodeBB running on 0.5.1 branch. Everything is up-to-date and I have the latest version from the branch.
When I run ./nodebb dev/watch/start it crashes at the end just before the ready.

This is the error, it seems that loader.js doesn't like callback.

info: [meta/css] Minifying LESS/CSS
info: [meta/css] Done.
info: [meta/templates] Compiling templates
info: [themes] Successfully compiled templates.

child_process.js:1023
    throw new Error('Unknown signal: ' + sig);
          ^
Error: Unknown signal: SIGCONT
    at ChildProcess.kill (child_process.js:1023:11)
    at ChildProcess.<anonymous> (c:\wamp\www\Github\NodeBB\loader.js:32:35)
    at ChildProcess.emit (events.js:98:17)
    at handleMessage (child_process.js:322:10)
    at Pipe.channel.onread (child_process.js:349:11)

Aurélien@ESIAO /c/wamp/www/Github/NodeBB (0.5.1)

Vanilla theme is also up-to-date I don't really know what's going on.

[julian]

Eh, does windows not support the SIGCONT signal? sigh...

gh#2029

[esiao]

It seems like so
This could help
http://stackoverflow.com/a/11010508

[julian]

Not to worry, I'm not using SIGCONT in the traditional sense, just as a way to signal the NodeBB child app that it can bind to the expected port.

[esiao]

@julian You just need to find another way thanks to Windows

[frissdiegurke]

@esiao said:

@julian You just need to find another way thanks to Windows

Why not just dropping windows support?

[julian]

@frissdiegurke Good idea

@esiao, can you try with commit 9ea081d on that branch?

[esiao]

@julian Yes I can, I don't see if I'm on 0.5.1 though. What are the key features to see it ?
(I've searched for sub-categories but didn't see them).

[julian]

You'll need to also check out the 0.5.1 branch of the vanilla theme as well.

• Reload button in ACP
• Subcategory selection in categories page of ACP
• Various other fixes