
Meteor 0.6.5 released
Meteor was repeatedly mentioned on the hub ( here , here and here ) - a high-level JavaScript framework for quickly creating single-page web applications.
Version 0.6.5 has been released today. Major changes:
We figured out the same with namespaces, mainly the changes affected the package namespace (see the documentation ). The concept has not changed: the application and each module have their own namespace. If global variables are needed - please (meteor wraps around your code, and the variables will be global either for the application or for the corresponding module). Variables with a "file" namespace are also supported - just declare a variable with var . When you connect the package, only export variables are visible, and in all the 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 way 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” - client and server of the DDP data synchronization protocol, “deps” - ultralight package that implements reactivity (instant update of the system when data changes), “ spark ”- a library that allows you to update the DOM when data changes. Until now, all modules have been added to each Meteor application at once - now this is not so. Now you can manually connect and disconnect kernel packages.
The Meteor build subsystem now boasts full support for “source maps”, now, for example, debugging support with full CoffeeScript sources in the browser goes right out of the box.
The current version eliminates a long-standing omission: server data files did not get into the assembly. Now it’s not so: put the data files that should be available on the server in the private folder , and they will become available through the Assets API.
The documentation is 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 back in 0.6.0, but was not documented) .
The full list of changes can be viewed here .
Version 0.6.5 has been released today. Major changes:
1. Namespaces and Modules
We figured out the same with namespaces, mainly the changes affected the package namespace (see the documentation ). The concept has not changed: the application and each module have their own namespace. If global variables are needed - please (meteor wraps around your code, and the variables will be global either for the application or for the corresponding module). Variables with a "file" namespace are also supported - just declare a variable with var . When you connect the package, only export variables are visible, and in all the 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 way 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” - client and server of the DDP data synchronization protocol, “deps” - ultralight package that implements reactivity (instant update of the system when data changes), “ spark ”- a library that allows you to update the DOM when data changes. Until now, all modules have been added to each Meteor application at once - now this is not so. Now you can manually connect and disconnect kernel packages.
3. Source maps
The Meteor build subsystem now boasts full support for “source maps”, now, for example, debugging support with full CoffeeScript sources in the browser goes right out of the box.
4. Attachments with data (Assets)
The current version eliminates a long-standing omission: server data files did not get into the assembly. Now it’s not so: put the data files that should be available on the server in the private folder , and they will become available through the Assets API.
Yet
The documentation is 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 back in 0.6.0, but was not documented) .
The full list of changes can be viewed here .