Using the variable name 'module' triggers a parse error about rapydscript HOT 3 CLOSED

module is indeed a reserved keyword, it's an explicit way of creating a module object that Python gives you implicitly when you put the code in a separate file. For things like module.exports overrides you could use JS('module').exports syntax.

from rapydscript.

Thanks for your reply. Unfortunately JS('module').exports doesn't seem to work:

WARN: ERROR: Unexpected token: punc «.» [tasks/rapydscript.pyj:9,12]

/home/lool0/grunt-test/lib/node_modules/rapydscript/lib/parse.js:122
    throw new JS_Parse_Error(message, line, col, pos);
          ^
Error
    at new JS_Parse_Error (/home/lool0/grunt-test/lib/node_modules/rapydscript/lib/parse.js:110:18)
    at js_error (/home/lool0/grunt-test/lib/node_modules/rapydscript/lib/parse.js:122:11)
    at croak (/home/lool0/grunt-test/lib/node_modules/rapydscript/lib/parse.js:702:9)
    at token_error (/home/lool0/grunt-test/lib/node_modules/rapydscript/lib/parse.js:705:9)
    at unexpected (/home/lool0/grunt-test/lib/node_modules/rapydscript/lib/parse.js:711:9)
    at /home/lool0/grunt-test/lib/node_modules/rapydscript/lib/parse.js:892:17
    at /home/lool0/grunt-test/lib/node_modules/rapydscript/lib/parse.js:742:20
    at Object.<anonymous> (/home/lool0/grunt-test/lib/node_modules/rapydscript/lib/parse.js:2320:23)
    at Object.parse (/home/lool0/grunt-test/lib/node_modules/rapydscript/lib/parse.js:2362:7)
    at /home/lool0/grunt-test/lib/node_modules/rapydscript/bin/rapydscript:241:36

JS('module.exports') compiles fine though so if you think there's nothing to be done here I don't mind closing this ticket. Thanks for all the work you guys have put into this project :). I'm very new to this whole javascript thing and programming in general, and this was for the first thing I wrote in rapydscript as part of my GSOC project: https://github.com/loolmeh/grunt-rapydscript (any feedback you guys can provide would be great)

from rapydscript.

JS('module.exports') will work fine as well, I'll take a look at the parsing for JS('module').exports to figure out what's wrong, RapydScript should have no problem referencing variables from function return. I haven't started using grunt yet but plan to check it out later (we've built out our own scripts for building/deploying, although they are getting a little dated).

from rapydscript.