Announcing Meteor 1.3.1

channels, channels, beta channels vs. “stealth” mode :wink:

2 Likes

thanks guys, keep’em coming :slight_smile:

Is this referring to the meteor run command? I’m assuming meteor build works as before.

+1 on ditching the stealth mode and using beta channels instead. This doesn’t follow semver and can be confusing. Or use something like 1.3.0.900 then count upwards from there until 1.3.1 is confirmed stable/final.

2 Likes

Great work MDG! Also, really loving this rapid-release cycle, keep 'em coming! :wink:

1 Like

@benjamn what about this issue about binary npm packages throwing errors when trying to deploy.

not being able to deploy is a pretty big problem and IMO way more important than CSS modules (sorry guys).

I agree. I’ve wasted the whole week trying to deploy a Meteor 1.3 app without success due to this error:

Working on that too!

3 Likes

Thanks for the update! Any chance of 1.3.1 or 1.3.x supporting Node 4?

1 Like

Is there a roadmap currently on what the next feature to be worked on? Just curious what you guys are planning beyond 1.3.1

Here’s the immediate stuff: https://github.com/meteor/meteor/milestones/Release%201.3.x

Upgrading Node and gradually migrating Meteor packages to npm are the next big priorities.

2 Likes

1.3.1 is recommended now. Type meteor update at your convenience!

3 Likes

@benjamn Do you know where I can find changelogs for this new version to see what was fixed and changed? (Can I import css styles from npm packages now?)

2 Likes

Here’s the 1.3.1 changelog.

Here’s what’s coming in 1.3.2.

2 Likes

Awesome! Good idea to make small progressive updates IMO.

Cordova iOS builds are no longer built by Meteor, but merely prepared for building.

What does that mean? How is it build now?

Thanks, I will bookmark History.md

I hope new build crud is something you’ll focus on if you’re planning on making more releases. Currently (on a 2015 MBP) every release requires that I reinstall Meteor as there’s always stuff left in ~/.meteor that slows builds down to a grinding halt (CSS refreshes taking anything between 10-30 seconds, app builds taking up to 1 minute). I noticed the easiest way is to just remove the entire .meteor directory and redownload everything but it is a bit of a bummer to do across 5 apps if you release every week.

Trying to update to 1.3.1 and getting a promise_server.js throw error. The error states that it is undefined. Anyone had issues with this?

updating to 1.3.1 and getting a promise_server.js throw error too.
TypeError: Cannot convert null to object

I restarted computer and freed up some disk space on my harddrive, and then navigated into my app folder and tried the process again. It worked. Try and make sure you have at least 1.5 gigs of space on your SSD or HDD, and try after a fresh restart. It has seemed to fix most updating problems for me

1 Like

This just means meteor build will now only generate the Xcode project, but won’t attempt to compile it. In order to code sign and submit to the App Store, you would always need to open the Xcode project, so this saves an unnecessary compile and also fixes a problem with our workaround for a Cordova bug (see here).