So will adding meteor-node-stubs make packages like stripe and aws-sdk work without issue?
thanks for clarification
@ffxsam aws-sdk yes, stripe almost. This line relies on the existence of a createServer() method in the http stub module, and expects that method to return an object with a .timeout property. Unfortunately http-browserify doesnât provide a stub implementation for that method, but thatâs exactly the kind of thing we can fix over at the meteor-node-stubs repository, without any coordination with Meteor.
I suppose you could also fix it in your own code, before importing stripe, by doing something like this:
require("http").createServer = function () {
// Same as https://github.com/nodejs/node/blob/04ac1c0c07/lib/_http_server.js#L239
return { timeout: 2 * 60 * 1000 };
};
1 Like
@etmarch nothing in ~/.meteor/packages is irreplaceable, unless you donât have an network connection, or someone rage-unpublishes a package left-pad-style⌠though Iâm not even sure we allow that 
Edit: As @shaym points out below, you should avoid deleting ~/.meteor/packages/meteor-tool, or you will have to reinstall Meteor.
9 Likes
When is the release coming, wonder whatâs coming first, my tax deadline or 1.3?
Last I heard, Monday was the target.
1 Like
dont delete the meteor-tool directory inside packages , it is used by the main meteor cli
1 Like
No more new features of any size will be going into this release, and we will do everything in our power to get it out the door next Monday morning. (March 28)
Cool I really am excited to get my hands on this new release.
@benjamn: will you use the same process for 1.4 and onward? By that I mean having an open public beta, encouraging everyone to test and report, find issues and suggest changes. It seems that it was really beneficial to advertise this beta, because many people participated and we hunted down a ton of stuff that could potentially creep in to stable release. And also the community input helped shape the release in a direction that most of us want it to be.
3 Likes
What are you waiting for? Meteor wonât be packaged in a box and put on amazon for sale. There is no âwaitingâ.
Just do:
meteor --release 1.3-rc.12 create mynewapp
Just use it and if you find an issue, post it on github like you normally would. There is no waiting no more on a release. Maybe for a particular feature (check github ticket) or a particular bug that hinders you from using something (check github ticket).
So, once and for all: Meteor is released. All the time. Just make use of the continuous delivery of incremental updates if you wish. If itâs not for feature / bug YXZ: donât wait. This ainât Apple.
1 Like
Yes! This long beta cycle was very illuminating. We (MDG) are eager to stop thinking of Meteor releases as big momentous milestones, so that we can ship better and better software as often as need be. 1.3.1 and 1.4 will definitely take the same approach.
7 Likes
Oh⌠now what am I gonna do with the $1000 worth of party supplies I bought in anticipation of the release?!
It could be that he is waiting for the updated docs. You donât have to bite his head off. He said he was excited, not that he was waiting to do an unboxing video. The release will make news / swing indirect factors into motion such as more awareness of npm, updated best practices, updated tutorials, etc. Iâm excited for 1.3 also and beyond.
3 Likes
meteor 1.3 released 
wondering how to update
2 Likes
Until 1.3 final release is out:
meteor update --release 1.3-rc.12I did meteor update --release 1.3 and it worked.
rc.12 is not the last rc, check the link: Meteor releases
3 Likes
Holy crap, 1.3 is out! Thanks for the heads up!
1 Like
I wonder why the 1.3 guide isnât released yet.
@sergiotapia: The 1.3 guide is already available under a versioned URL. Weâll switch the default docs and guide over when 1.3 is officially announced (probably morning PST).
3 Likes