mup - npm Package Compare versions

Comparing version 0.6.1 to 0.6.3

package.json

 {
   "name": "mup",
-  "version": "0.6.1",
+  "version": "0.6.3",
   "description": "Production Quality Meteor Deployments",
@@ -5,0 +5,0 @@ "dependencies": {

README.md

@@ -26,2 +26,3 @@ # Meteor Up
 - [Troubleshooting](#troubleshooting)
+- [Binary Npm Module Support](#binary-npm-module-support)
 
@@ -265,1 +266,13 @@ ### Features
 where `<command>` is one of the `mup` commands such as `setup`, `deploy`, etc.
+
+### Binary Npm Module Support
+
+Some of the Meteor core packages as well some of the community packages comes with npm modules which has been written `C` or `C++`. These modules are platform dependent. 
+So, we need to do special handling, before running the bundle generated from `meteor bundle`.
+(meteor up uses the meteor bundle)
+
+Fortunately, Meteor Up **will take care** of that job for you and it will detect binary npm modules and re-build them before running your app on the given server.
+
+> * Meteor 0.9 adds a similar feature where it allows package developers to publish their packages for different architecures, if their packages has binary npm modules.
+> * As a side effect of that, if you are using a binary npm module inside your app via `meteorhacks:npm` package, you won't be able to deploy into `*.meteor.com`.
+> * But, you'll be able to deploy with Meteor Up since we are re-building binary modules on the server.

No alert changes

Improved metrics

Total package byte prevSize

37770

increased by6.9%

Number of lines in readme file

277

increased by4.92%

No dependency changes