Blaze compile errors completely silent if imported

[TMeerhof]

In version 1.8 when compiling a blaze template from the /imports directory all errors are swallowed breaking the normal development process, because you get no line numbers or error specifications.

In 1.7 this problem is not present.

Reproduction:
Create a new meteor 1.8 project.

create a new malformed blaze template in the client folder.

<template name="test">
   {{#if}
</template>

You will get a compile error

Errors prevented startup:
   
   While processing files with templating-compiler (for target web.browser):
   client/test.html:2: Expected `}}`

Now move the file to /imports/client and add the import statement import '/imports/client/test.html'; to main.js.

There is no compile time error, but when running the app you get the following run time error
Uncaught Error: Cannot find module '/imports/client/test.html'.

[TMeerhof]

this is also the case for .less files, here you will get the even more criptic error:

internal/process/next_tick.js:131
      callback();

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed it has not had recent activity.

[zenhack]

I'm still seeing this issue as of meteor 2.0; can we reopen this?

[haveaguess]

Agreed I have to refactor my files out of import to see what the error is and then refactor them back, very tedious

[StorytellerCZ]

Seems to be the same issue as in meteor/meteor#10366

[StorytellerCZ]

@zodern do you have any plans for this issue?

[StorytellerCZ]

@zodern @jankapunkt maybe we should move this to the Blaze repository?

[jankapunkt]

I agree 👍