In all files, the default is specified at the beginning:

import { Meteor } from 'meteor/meteor';

Etc.

But even without this insert, everything works. Why meteor, then it took ... It is necessary for the IDE, for performance or something else? I can not understand.

Tell, please, I will be very grateful :)

    1 answer 1

    The global object Meteor and others are left for backward compatibility with previous versions. Write this import everywhere because:

    1. Rejection of global variables is the right approach: explicit import simplifies reading the code, reduces the number of errors.
    2. In one of the subsequent releases, global variables, such as the Meteor object, can simply be removed and, after updating, your application will stop working if you used global variables without import.
    • How, by the way, is the situation with the update in meteor? I read that very badly. It was a long time, but how now, better? When updating a lot need to solve problems? It is interesting as in large projects, although in small ones - of course. - Sergey Saveliev
    • one
      @ Sergey Saveliev with 1.3 I do not remember any special problems with the update. The updates are now mostly new features and bugfixes. - Igor Golovin
    • Say, the projects that you updated, how large? About how many files? What is the attendance? - Sergey Saveliev
    • Just if there are hundreds of files, as it will be very inconvenient ... - Sergey Saveliev
    • one
      150-200 files, look at the version history, it will be change what github.com/meteor/meteor/blob/devel/History.md - by Igor Golovin