Meteor 0.6.5 released
On Habré, Meteor was repeatedly mentioned ( here , here and here ) - a high-level JavaScript-framework for quickly creating single-page web applications.
Today version 0.6.5 was released. Major changes:
Understood with name spaces, generally changes concerned a name space of packets (see the documentation ). The concept has not changed: the application and each module have their own namespace. If you need global variables - please (meteor wraps around your code, and the variables will be global for either the application or the corresponding module). Variables with a “file namespace” are also supported — just declare a variable with var . When you connect a package, only export variables are visible, and in all files of your application. In other words, use meteor add and everything will work as you expect.
The most interesting thing is that everything works the same on the server and on the client, as they say, out of the box.
')
From the very beginning, the Meteor core was implemented as a set of independent modules that could be used separately or all together: “livadata” - the client and server of the DDP data synchronization protocol, “deps” - an ultra-light package that implements reactivity (instant system update when the data changes), “ spark ”is a library that allows you to update DOM when data changes. Until now, all modules were added to every Meteor application at once - now this is not the case. Now you can manually connect and disconnect the kernel packages.
The Meteor build subsystem now boasts full support for source maps, for example, now debugging support with full CoffeeScript sources in the browser goes straight out of the box.
The current version eliminated a long-standing omission: the server data files did not fall into the assembly. Now not so: put the data files that should be available on the server in the private folder, and they will be available through the Assets API.
The documentation is also naturally supplemented, for example, a section on package development appeared - http://docs.meteor.com , in particular, it finally describes how to use npm-modules (this feature appeared as early as 0.6.0, but was not documented) .
Full list of changes can be viewed here .
Today version 0.6.5 was released. Major changes:
1. Namespaces and Modules
Understood with name spaces, generally changes concerned a name space of packets (see the documentation ). The concept has not changed: the application and each module have their own namespace. If you need global variables - please (meteor wraps around your code, and the variables will be global for either the application or the corresponding module). Variables with a “file namespace” are also supported — just declare a variable with var . When you connect a package, only export variables are visible, and in all files of your application. In other words, use meteor add and everything will work as you expect.
The most interesting thing is that everything works the same on the server and on the client, as they say, out of the box.
')
2. Standard packages (standard-app-packages)
From the very beginning, the Meteor core was implemented as a set of independent modules that could be used separately or all together: “livadata” - the client and server of the DDP data synchronization protocol, “deps” - an ultra-light package that implements reactivity (instant system update when the data changes), “ spark ”is a library that allows you to update DOM when data changes. Until now, all modules were added to every Meteor application at once - now this is not the case. Now you can manually connect and disconnect the kernel packages.
3. Source maps
The Meteor build subsystem now boasts full support for source maps, for example, now debugging support with full CoffeeScript sources in the browser goes straight out of the box.
4. Data Attachments (Assets)
The current version eliminated a long-standing omission: the server data files did not fall into the assembly. Now not so: put the data files that should be available on the server in the private folder, and they will be available through the Assets API.
Still
The documentation is also naturally supplemented, for example, a section on package development appeared - http://docs.meteor.com , in particular, it finally describes how to use npm-modules (this feature appeared as early as 0.6.0, but was not documented) .
Full list of changes can be viewed here .
Source: https://habr.com/ru/post/190142/
All Articles