Compile time errors not show the file fullpath on packages that use `ecmascript`


#1

When I build my project if any compile time error is found Meteor put something like this:

=> Errors prevented startup:

   While processing files with ecmascript (for target web.browser):
   lib/afiliado.js:36:2: lib/afiliado.js: Unexpected token (36:2)

On large projects is difficult know on what package this file is.

Can I set any option to show full filepath?
Experienced developers has any advice on this question?


#2

usually it is the full path. are you sure your lib/afiliado.js row ne 36 is fine? And the lines before have all their brackets and everything?


#3

The issue is not about a syntax error. Is about Meteor build console output.
Say I have many files with same name on many packages …
Ex:

packages/
       package-one/
           lib/
            afiliado.js
       package-two/
          lib/
           afiliado.js
       package-three/
          lib/
           afiliado.js

Is hard to know where is the error …


#4

I introduce a token into a page to break it, I get path info

Errors prevented startup:

While computing assigned variables:
/packages/maev_modal-semantic-ui/client/maev-modal.js: Unexpected token (5:0)


#5

@garrilla How do you run meteor project?
Here
$ meteor


#6

same here

running 1.2.0.2


#7

I create a meteor issue about: https://github.com/meteor/meteor/issues/5551

Any one solved this??