* Add mongo-dev-server package
Only start the MongoDB server if this package
is present in the project.
* Small layout/formatting adjustments; updated README.
* Allow tests using fake-mongod to start (fake) Mongo.
* Adjust test stdout matching to be less sensitive to ordering.
* Add `mongo-dev-server` History.md entry.
* Remove mongo start check since the tested for error prevents mongo startup.
* Remove README traling whitespace.
* Bump mongo package version.
* Add mongo-dev-server package
Only start the MongoDB server if this package
is present in the project.
* Small layout/formatting adjustments; updated README.
* Allow tests using fake-mongod to start (fake) Mongo.
* Adjust test stdout matching to be less sensitive to ordering.
* Add `mongo-dev-server` History.md entry.
* Remove mongo start check since the tested for error prevents mongo startup.
* Remove README traling whitespace.
* Bump mongo package version.
The suggestion to `meteor add` and then `meteor remove` is no longer
relevant with the addition of the awesome new `--extra-packages`
option from @mpowaga in meteor/meteor#8769.
When checking the `entriesByIno` Map to see if an `entry` already exists for
the specified inode, also check to make sure the found `entry` is only
re-used if the current file watcher path matches the returned path. This
makes sure new file watchers are created for moved files (so files with the
same inode), instead of attempting to re-use a file watcher that's watching
an invalid path.
Node 8 is more aggressive than Node 4 about displaying
UnhandledPromiseRejectionWarning messages, and we were making no effort to
handle rejections here.
As a bonus, we now try to start and connect to Mongo up to three times,
rather than giving up the first time.
We should never be generating line number comments for server code, since
they can cause problems with multi-line strings, and no one will see those
comments on the server anyway.
The html-scanner tests were breaking because we no longer compile
multi-line template strings for Node 8, yet we were annotating every line
with a line number comment (because we had a source map), and lines within
multi-line template strings were getting comments appended to them, which
thus became an observable part of the string.
On the client, we still compile template strings to normal string
literals, so the line number annotations are not a problem (for now).
Related to https://github.com/meteor/meteor/pull/8728#issue-232369984,
though these changes apply only to the meteor/tools codebase. We still
need to make similar changes to the babel-compiler package so that
application code will benefit.
The assumption that we're using Node 8 also allows some simplifications to
the runtime polyfills that we use.
* Fix CircleCI failures by adjusting the timing of problematic tests.
* Wait longer for Mongo to start.
* Increase lint wait time; run logs show we're close to the current timeout.
