That Full Lint ejs sounds really useful. I wasn't able to figure out any way to get it to work either, though, and on the project's forum there's a thread from last year which suggests it might not be working at all.
As a possible alternative workaround, if you aren't currently pulling in your .ejs files via steal() then doing so might give you better error messages. There still aren't exact line numbers, and it's still within eval(), but when there's a syntax error or other mistake you get the real javascript error and you can sometimes see the actual bit of code which caused it.
Compared to our project's original approach with <script type="text/ejs"> tags for ejs content, the improved messages were so much better that it immediately cinched our decision to go with stealjs. Further debugging and line numbers with errors would definitely be nice, though.
As a possible alternative workaround, if you aren't currently pulling in your .ejs files via steal() then doing so might give you better error messages. There still aren't exact line numbers, and it's still within eval(), but when there's a syntax error or other mistake you get the real javascript error and you can sometimes see the actual bit of code which caused it.
Compared to our project's original approach with <script type="text/ejs"> tags for ejs content, the improved messages were so much better that it immediately cinched our decision to go with stealjs. Further debugging and line numbers with errors would definitely be nice, though.