Meteor 1.3 is backwards compatible so will run as expected without import statements, but moving towards import/export is the recommended path forward and in the future the eager loading of js files may be removed in favor of lazy loading.
thank you. I understand that. But how is it that the old files still work? Does it automatically do an import {Meteor} on all ‘eagerly loaded’ js files, or only on some of them?
I understand that my other files, not in /imports are automatically loaded. But does the compiler automatically include ‘meteor/meteor’ into those automatically loaded files? And if so, then what else does it automatically include in those files?
It’s not adding any import statements, it’s just that your code gets all put into one file where global variables are now in all of your file’s scopes and can then be used throughout your app.
I agree it is not clear from the new Meteor 1.3 Guide what the default bundling and load order is for apps built without using import and that all Meteor objects are still accessible as globals. I’m writing an update to the Guide to make this more clear. See Application Structure
Thanks. This clarifies whats happening better now. This will make it easier for me to determine if and when I need to import explicitly. Thanks for everyones input.