Blake Miner

Yeah, I'll take you up on that! I'll let you know once I come up with a plan to move forward. I think I have your email.

Ewww... `:` and `@` are not supported by XHTML in the attribute name as far as I know. I'm not quite sure about HTML5. I don't really want to support...

Hm, alright. If it's a Vue thing, I suppose the Blade parser should support it. Have you ever tried [Riot.js](http://riotjs.com)?

Just following up. Would you be willing to do a PR for this? It would likely involve updating the PEG.js parser rules. If you're uncomfortable doing so, I don't blame...

I agree with you; this should be a configurable option in Blade (perhaps even off by default). I just opened the issue so that I wouldn't forget about it later.

**Update:** Google V8 now provides more detailed error information for `eval`ed JavaScript code. Hopefully, this capability will be added to Node shortly... Google V8 3.12.0 fixes issue 1914.

**Update:** This feature will probably not be added to Node v0.8; it will likely appear in Node v0.9.

~~**Update:** This feature will likely be added in the Node v0.9.3 release. It has been added to the node master branch.~~ **Correction:** This issue has not yet been fully resolved...

@lenzhang - That's probably true. I have not yet tested on Node v0.9.x. Will keep you posted.

@lenzhang - As it turns out, Google V8 3.12 revealed line and column numbers for runtime errors, not for compilation/parsing errors. I will continue to work with the V8 crew...