Meteor is een JavaScript framework met server-side en client-side ondersteuning, waarin je complete webapplicaties kan ontwikkelen voor Linux, Windows, macOS, Android en iOS, inclusief ondersteuning van databases zoals MongoDB. Voor de server-side wordt Node.js gebruikt, voor de client-side jQuery. Voor meer informatie verwijzen we jullie door naar deze pagina. Het ontwikkelteam heeft versie 1.6.1 van Meteor uitgebracht voorzien van de volgende aankondiging:
Announcing Meteor 1.6.1
Babel 7, Cordova 7.1, Mongo 3.4, streaming server rendering, and more
Today we’re pleased to announce Meteor 1.6.1, an incremental release that’s packed with small improvements, as well as one important upgrade that requires special explanation: Babel 7
Meteor 1.6.2 is already well underway, because we didn’t get everything we wanted into Meteor 1.6.1. However, Meteor 1.6.1 was becoming quite a large release (486 commits, even more than Meteor 1.6), so we decided to shift gears, stabilize the moving parts, and release everything finished so far.
A note about versioning
If you’re not familiar with Meteor’s versioning conventions, releases like 1.5 or 1.6 are considered significant Meteor releases, meaning you should do everything in your power to upgrade your applications, because we’ve changed some very important aspects of how Meteor works.
Most software projects indicate major changes with versions like 2.0 or 16, but here at Meteor we’ve tried incredibly hard to preserve backwards compatibility ever since Meteor 1.0, so we’re saving “2.0” for a version of Meteor that requires profound changes to existing code. Until then, “minor” versions like Meteor 1.6 represent our most exciting releases.
According to this convention, Meteor 1.6.1 is an incremental release that fixes bugs and implements relatively conservative new features (relative to Meteor 1.6). Meteor 1.6.1 is a great version for starting a new application, and should be an appealing update if you’re already on the latest previous version (1.6.0.1), though it is not absolutely obligatory. Speaking of Meteor 1.6.0.1, a four-digit version represents a minimal patch release that fixes a critical problem for some set of Meteor developers, such as a security update to a bundled dependency like Node.js.
In other words, you should update to Meteor 1.6.1 if it fixes a problem for you, or you need any of the new features it provides, or just because you feel like staying up to date, after consulting the release notes or reading the rest of this blog post to get the highlights.
Babel 7
By far the most noticeable change in Meteor 1.6.1 is that we’ve upgraded the version of Babel used for compiling ECMAScript package and application code from 6.24.7 to 7.0.0-beta.38. Yes, that’s a beta version, but we believe that’s acceptable for several reasons:Other improvements
- We will be able to republish the babel-compiler and ecmascript packages to use a non-beta version of Babel whenever 7.0.0 is finalized, without having to publish a new Meteor release.
- Other projects, such as React, have already begun to recommend Babel plugins that depend on Babel 7, such as @babel/plugin-transform-react-jsx
- Meteor has been using beta versions of Babel to implement the meteor command-line tool ever since Meteor 1.6, which has given us a chance to identify and fix the handful of problems we’ve encountered so far.
- By leveraging the abstractions of meteor-babel and babel-preset-meteor, as well as shrink-wrapping all of their dependencies, Meteor is able to provide a consistent core of well-tested Babel plugins, which shields Meteor developers from much of the complexity of the changing Babel plugin ecosystem.
Instead of enumerating the many other changes in this release, we encourage you to read the release notes.
We’ve updated Cordova, Mongo, and many of the npm packages used by Meteor packages and the meteor command-line tool. Dynamic import() now uses HTTP POST requests. Thanks to James Baxley III, the server-render package now supports passing a Stream object to ServerSink methods that previously expected a string, which enables streaming server-side rendering with React 16.
Conclusion
As long as your application is committed to version control, so that you can roll back in case of problems, there’s no harm in running meteor update to see what happens. Who knows; you might not even notice the Babel 7 update. Your application is unique among all Meteor applications.
If you run into any problems with the update, or have any questions, feel free to open an issue, comment on the Meteor 1.6.2 pull request, or start a discussion on our forums, and we will do everything in our power to help make Meteor 1.6.1 (or at least Meteor 1.6.2) work for you.
:strip_exif()/i/2001533999.png?f=thumbmedium)