I installed spider-script through npm, but `spider somescript.spider` complains with $traceurRuntime not being defined. I can still compile the script, then req

I installed spider-script through npm, but `spider somescript.spider` complains with $traceurRuntime not being defined. I can still compile the script, then require traceur and the script from another file, but I'd rather not have to do that just to try out the language :( The FizzBuzz example is (still) bugged: it lacks semicolons and []s around [1...100]. Now for my thoughts: I like the way you handle globals, channels and async/await. Currying syntax is nifty, I probably wouldn't have chosen ^ but that's a bit of an arbitrary choice I guess. For integer division I prefer //, but I just realized you use that for comments. The module syntax works, although I prefer to group export declarations in a separate export or provide block. I think the pattern matching is insufficiently powerful. Normally, pattern matching lets you declare variables as part of the pattern, so that it becomes a kind of switch on the different ways to deconstruct the input. I have an example of what I mean here: http://jsfiddle.net/f1ycatas/2/ http://jsfiddle.net/f1ycatas/2/ . Matching the value of an existing variable could be done with syntax like `== n`.