<div dir="ltr">I've been kicking the tires of v4.0.0 using my applications. So far so good, nothing broken. <div><br></div><div>However enough is different from v0.12.x and v4.0.0 that it might be wise to be careful about upgrading too quickly.</div><div><br></div><div>+ David Herron</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 15, 2015 at 3:12 PM, Thad Humphries <span dir="ltr"><<a href="mailto:thad.humphries@gmail.com" target="_blank">thad.humphries@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">With the recent release of <a href="https://nodejs.org/en/blog/release/v4.0.0/" target="_blank">Node.js v4.0.0 (Stable)</a>, how will the <a href="https://www.macports.org/ports.php?by=library&substr=nodejs" target="_blank">current nodejs package</a> be upgraded? I'd rather stick with MacPorts vs downloading the Mac package from <a href="http://nodejs.org" target="_blank">nodejs.org</a>.<span class="HOEnZb"><font color="#888888"><div><div><div><br></div>-- <br><div><div dir="ltr">"Hell hath no limits, nor is circumscrib'd In one self-place; but where we are is hell, And where hell is, there must we ever be" --Christopher Marlowe, <i>Doctor Faustus</i> (v. 121-24)</div></div>
</div></div></font></span></div>
<br>_______________________________________________<br>
macports-users mailing list<br>
<a href="mailto:macports-users@lists.macosforge.org">macports-users@lists.macosforge.org</a><br>
<a href="https://lists.macosforge.org/mailman/listinfo/macports-users" rel="noreferrer" target="_blank">https://lists.macosforge.org/mailman/listinfo/macports-users</a><br>
<br></blockquote></div><br></div>