meteor v1.4.4.2 Release Notes
Release Date: 2017-05-02 // almost 7 years ago-
⬆️ Node has been upgraded to version 4.8.2.
⬆️ The
npm
npm package has been upgraded to version 4.5.0. Note that when using npmscripts
there has been a change regarding what happens whenSIGINT
(Ctrl-C) is received. Read more here.🛠 Fix a regression which prevented us from displaying a helpful banner when running
meteor debug
because of a change in Node.js.⚡️ Update
node-inspector
npm to 1.1.1, fixing a problem encountered when trying to press "Enter" in the inspector console. Issue #8469📦 The
email
package has had itsmailcomposer
npm package swapped with a Node 4 fork ofnodemailer
due to its ability to support connection pooling in a similar fashion as the originalmailcomposer
. Issue #8591 PR #8605Note: The
MAIL_URL
should be configured with a scheme which matches the protocol desired by your e-mail vendor/mail-transport agent. For encrypted connections (typically listening on port 465), this means usingsmtps://
. Unencrypted connections or those secured through aSTARTTLS
connection upgrade (typically using port 587 and sometimes port 25) should continue to usesmtp://
. TLS/SSL will be automatically enabled if the mail provider supports it.A new
Tracker.inFlush()
has been added to provide a global Tracker "flushing" state. PR #8565.⬆️ The
meteor-babel
npm package has been upgraded to version 0.20.1, and thereify
npm package has been upgraded to version 0.7.4, fixing issue #8595. (This was fixed between full Meteor releases, but is being mentioned here.)