Quantcast
Channel: Appcelerator Developer Center Q&A Unanswered Questions 20
Viewing all articles
Browse latest Browse all 8068

Getting more helpful error messages / Alloy

$
0
0

I started a while back using Alloy and I have to admit that its lack of meaningful error messages is just incredibly annoying. When I get as an output something like this:

[DEBUG] :  module.exports = Controller;
[DEBUG] :  
[DEBUG] :  /usr/local/lib/node_modules/alloy/Alloy/commands/compile/sourceMapper.js:100
[DEBUG] :       throw e;
[DEBUG] :             ^
[ERROR] :  
[ERROR] :  (/usr/local/lib/node_modules/alloy/node_modules/uglify-js/lib/parse.js:185:18)
[ERROR] :  (/usr/local/lib/node_modules/alloy/node_modules/uglify-js/lib/parse.js:199:11)
[DEBUG] :      at croak (/usr/local/lib/node_modules/alloy/node_modules/uglify-js/lib/parse.js:630:9)
[ERROR] :  (/usr/local/lib/node_modules/alloy/node_modules/uglify-js/lib/parse.js:638:9)
[DEBUG] :      at unexpected (/usr/local/lib/node_modules/alloy/node_modules/uglify-js/lib/parse.js:644:9)
[DEBUG] :      at semicolon (/usr/local/lib/node_modules/alloy/node_modules/uglify-js/lib/parse.js:664:43)
[DEBUG] :      at simple_statement (/usr/local/lib/node_modules/alloy/node_modules/uglify-js/lib/parse.js:822:73)
[DEBUG] :      at /usr/local/lib/node_modules/alloy/node_modules/uglify-js/lib/parse.js:707:19
[DEBUG] :      at /usr/local/lib/node_modules/alloy/node_modules/uglify-js/lib/parse.js:677:24
[DEBUG] :      at block_ (/usr/local/lib/node_modules/alloy/node_modules/uglify-js/lib/parse.js:938:20)
[ERROR] :  Alloy compiler failed
It feels completely useless, as I don't even know which specific file it is about. Is there any secret magic to understand Alloy error messages that I am missing?

Viewing all articles
Browse latest Browse all 8068

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>