import { Meteor } from ‘meteor/meteor’ (meteor/client_environment.js, line 49)
As far as I understand, all imports are loaded somewhere at startup and exported somewhere first. Where can I see both exports and imports, which constitute Meteor?
Yes, 1.3 is designed to be backwards compatible. The imports folder is for all the imports and exports that are not eagerly loaded but are imported into the app as you define. The imports on your point 2, is for files that are in the imports folder.
Kind of, but it’s not just informational. If the import line is present, then it guarantees the source. So if at a later stage, a different global variable of the same name is introduced, the file won’t break.
It also means, moving forward, that you don’t need to resort to crazy names to get files to load in the right order, makes the code easier to test, analyse and work with, also with tools from the wider ecosystem and potential future improvements. e.g. you could never do “tree shaking” (like e.g. rollup.js) by relying on globals. So it’s a big improvement for us