import from modules don't work
When you import a module (say, A) in a module (say, B) that’s not an application (i.e., not the “root module”, so to speak), then the loading of A is not triggered, resulting in a not-so-clear JS error.
Submitted by Meinte Boersma on 14 March 2011 at 21:35
Issue Log
On 14 March 2011 at 21:39 Zef Hemel commented:
It will loaded after you recompile the application module. That’s a problem yes, we need better detection of required recompilation for sure.
On 14 March 2011 at 21:44 Meinte Boersma commented:
Ah, I see now. (I thought the behavior was that you have to import A in the application module to get it working.) So, this issue falls under the transitive compilation issue, right?
On 14 March 2011 at 21:44 Zef Hemel commented:
Indeed.
On 16 March 2011 at 15:26 Meinte Boersma commented:
And just to be sure: the type/American-Afrocanism in the issue’s title is due to careless editing of that ;)
On 16 March 2011 at 15:27 Zef Hemel commented:
Sure it is…
Log in to post comments