If you haven’t noticed Meteor 1.8.1 has been released. Here is the list of changes from the history file:
- Although we are not aware of any specific backwards incompatibilities,
the major upgrade of
cordova-androidfrom 6.4.0 to 7.1.4 likely
deserves extra attention, if you use Cordova to build Android apps.
Note: While Node 8.12.0 included changes that may improve the
performance of Meteor apps, there have been reports of CPU usage spikes
in production due to excessive garbage collection, so this version of
Meteor should be considered experimental until those problems have been
fixed. Issue #10216
Mongo has been upgraded to version 4.0.6 for 64-bit systems (was 4.0.2),
and 3.2.22 for 32-bit systems (was 3.2.19). The
npm-mongohas been updated to version 3.1.13 (was 3.1.6).
fibersnpm package has been updated to version 3.1.1, a major
update from version 2.0.0. Building this version of
C++11 compiler, unlike previous versions. If you deploy your Meteor app
manually (without using Galaxy), you may need to update the version of
g++used when running
npm installin the
meteor-babelnpm package has been updated to version 7.3.4.
Cordova Hot Code Push mechanism is now switching versions explicitly with
WebAppLocalServer.switchToPendingVersioninstead of trying to
switch every time a browser reload is detected. If you use any third
party package or have your own HCP routines implemented be sure to call
it before forcing a browser reload. If you use the automatic reload from
Reloadmeteor package you do not need to do anything.
cordova-plugin-meteor-webapp PR #62
Multiple Cordova-related bugs have been fixed, including Xcode 10 build
incompatibilities and hot code push errors due to duplicated
images/assets. PR #10339
cordova-iosnpm dependencies have been
updated to 7.1.4 (from 6.4.0) and 4.5.5 (from 4.5.4), respectively.
meteor mongocommand no longer uses the
--quietoption, so the
normal startup text will be displayed, albeit without the banner about
Mongo’s free monitoring service. See this
MongoDB Jira issue
for more details.
In Meteor packages,
server/directories no longer have
any special meaning. In application code,
ignored during the server build, and
server/directories are ignored
during the client build, as before. This special behavior previously
applied to packages as well, but has now been removed.
If your application is using Git for version control, the current Git
commit hash will now be exposed via the
while the app is running (in both server and client code), and also via
"gitCommitHash"property in the
star.jsonfile located in the
root directory of builds produced by
meteor build, for consumption by
deployment tools. If you are not using Git, neither property will be
defined. PR #10442
x-no-compressionrequest header will prevent the
package from compressing responses with
gzip, which may be useful if
your Meteor app is behind a proxy that compresses resources with another
compression algorithm, such as brotli.
Coming up next is Meteor 1.9 for which we already have a milestone:
And finally don’t forget to check out a new blog post on the Meteor Blog from @pcorey :