I understand the idea behind importing CSS in order to control load order. But everything in Meteor is tucked into template files and templates are ordered and arranged according to some layout.
What good does importing HTML do? Or are we just loading it as a formality in the example app?
Also load order. In the example app, you’ll see that the JS refers to
Template.somethingFromImport. That Template is only guaranteed to be available after calling the import statement first. It might be available anyway due to Meteor’s old magic load order rules, but not if you’re files are in the
What’s also confusing is that templates get attached to the
Template global. What’s a lot better is nathantreid’s Blaze modules, which behave a bit more like what you’d expect in a proper modules environment.
Ooh this is really nice! Thanks for the detailed reply @gadicc. And for the groovy link. :3