Fix error on Meteor.loginWithGoogle() with no args
Workaround issue with new node and old connect. Fixes #852

New node (0.8.21+) throws an error when path.join is passed null. Connect 1.9.2's static.send (used by gzippo) does this if you don't pass a 'root' option. Passing root: '/' works around this, but we should consider fixing the underlying issue, possibly by upgrading connect.
Add explicit safety check for non-object modifiers passed to update.
demo of login and private data
more readme
log errors from login (eg not configured)
fix error logging in login-demo
Clarify Meteor.startup documentation.

Fixes #831.
minor wordsmithing
Merge pull request #878 from 'awwx/clarify-startup-docs' into devel
remove leftover comment
Merge branch 'pr/877' into devel

Closes #877
Stop accounts-ui <input> CSS from leaking to whole app
Fix function name typo in docs.
Remove list of names from docs.
Whitelist allowed update operators in validated updates.
background update check, now with print-once-only banner
We can assume there is always a latest release installed now.
Don't assign to exports. That breaks circular requires.
make TEST_WAREHOUSE_DIR a non-test thing called METEOR_WAREHOUSE_DIR

(the non-springboarding piece of that is now controlled by
METEOR_TEST_NO_SPRINGBOARD)

This means that run-all-tests.sh can use launch-meteor to bootstrap a warehouse
instead of starting with an empty warehouse directory (which is no longer
allowed).

also, fix npm module usage out of the bootstrap tarball: we were too liberal in
the "never update npm dependencies in the warehouse" rule since the bootstrap
tarball would contain packages with no node_modules (or if we had a failure
between downloading a package and running installNpmDependencies).  instead,
"never update npm dependencies in the warehouse if .npm/node_modules already
exists".