Windows does not support uglify. It only runs with the -r switch.

[blargism]

Here's the error. If I add the -r switch it compiles and watches just fine.

The command that fails
handlebar-rider -i ".\templates" -o ".\templates.js" -w

Environment
Windows 8 nodejs command prompt version 0.8.16

Error
at new JS_Parse_Error (C:\Users\Joe\AppData\Roaming\npm\node_modules\handlebar-rider\n
ode_modules\uglify-js\lib\parse-js.js:260:22)
at js_error (C:\Users\Joe\AppData\Roaming\npm\node_modules\handlebar-rider\node_module
s\uglify-js\lib\parse-js.js:268:15)
at parse_error (C:\Users\Joe\AppData\Roaming\npm\node_modules\handlebar-rider\node_mod
ules\uglify-js\lib\parse-js.js:359:17)
at hex_bytes (C:\Users\Joe\AppData\Roaming\npm\node_modules\handlebar-rider\node_modul
es\uglify-js\lib\parse-js.js:418:33)
at read_escaped_char (C:\Users\Joe\AppData\Roaming\npm\node_modules\handlebar-rider\no
de_modules\uglify-js\lib\parse-js.js:407:59)
at C:\Users\Joe\AppData\Roaming\npm\node_modules\handlebar-rider\node_modules\uglify-j
s\lib\parse-js.js:445:51
at with_eof_error (C:\Users\Joe\AppData\Roaming\npm\node_modules\handlebar-rider\node_
modules\uglify-js\lib\parse-js.js:581:32)
at read_string (C:\Users\Joe\AppData\Roaming\npm\node_modules\handlebar-rider\node_mod
ules\uglify-js\lib\parse-js.js:425:24)
at Object.next_token [as input](C:UsersJoeAppDataRoamingnpmnode_moduleshandleb
ar-ridernode_modulesuglify-jslibparse-js.js:596:52)
at next (C:\Users\Joe\AppData\Roaming\npm\node_modules\handlebar-rider\node_modules\ug
lify-js\lib\parse-js.js:706:37)
at subscripts (C:\Users\Joe\AppData\Roaming\npm\node_modules\handlebar-rider\node_modu
les\uglify-js\lib\parse-js.js:1169:25)

[piercemoore]

I am on this issue, this is actually my boss at work and not a random internet stranger. We found this bug today and I asked him to log it.

Commit 028b299 fixed the Windows directory separator bug, but it turns out that UglifyJS has WAY more issues than that. It just doesn't want to run properly. So I'm going to dig a bit and check it out.

[blargism]

I'm guessing it has to do with directory separators as well. I think the suggestion of just disabling uglify on windows is a good one for the short term.