The main benefit for using imports is you can define the load order of the files rather than relying on meteor to do it for you. It may be a bit counter-intuitive in most cases, but it does make things more predictable.
In addition, using imports will allow you to avoid implicit globals in your code so linters would have an easier time.
To be really clear, if you use the structure with the âimportsâ directory, you must use imports in your code because files under any imports directory are not loaded unless explicitly included by import or require.
Furthermore, if youâre writing new code and believe youâll continue using meteor beyond 1.3, IMO it would be wise to use the modular structure (imports) now because there is an expectation that a future release will lazy load files from all directories, not just the imports directory.
Youâll find many opinions as to the advantage(s) of modular structure. IMO it keeps the namespace cleaner and I like the explicit indication of dependencies in every file. Of course, I cut my teeth on languages like Pascal and Ada and applications with millions of lines.