Add reference to meteor-node-stubs in migration guide meteor#314

content/1.3-migration.md

@@ -36,6 +36,12 @@ import { Meteor } from 'meteor/meteor';
 import { EJSON } from 'meteor/ejson';
 ```
 
+- You should consider installing the `meteor-node-stubs` npm package to allow using npm packages written for `node` on the browser: 
+
+```bash
+meteor npm install --save meteor-node-stubs
+```
+
 - If you are using app-local packages to control load order and write unit tests for your application, we recommend you switch to using modules. You can read about our recommended structure for applications and modules in the [Application Structure article](structure.html) of the Meteor Guide, and how to test them in the [Testing article](testing.html).
 
 - If you are using Atmosphere packages which simply wrap npm packages, both on the client and server, it is now recommended that you simply install them using npm. Run `npm init` to initialize your `package.json` and install packages with `npm install --save` (or `npm install --save-dev` if it's development dependency for testing etc.). We have [some tips](using-packages.html#async-callbacks) about how to use npm packages written in an asyncronous style.