The react-dom@16 npm package recently got stricter about how it checks
that dead code elimination is enabled. Specifically, it no longer just
checks that process.env.NODE_ENV is replaced with "production" but also
requires conditional branches to be completely removed if the replacement
makes them unreachable:
https://github.com/facebook/react/blob/master/packages/react-dom/npm/index.js
The minifier-js package recently had its minor version bumped for Meteor
1.6, so I think it's safe to enable dead code elimination in a patch
version update. If we bumped the minor version again (to 2.3.0), this
version of minifier-js would not be usable with Meteor 1.6, and would
probably have to wait for Meteor 1.6.1.
Bumping the patch version of standard-minifier-js is also necessary
because it uses minifier-js as a compiler plugin, and would otherwise
continue to bundle the old minifier-js plugin.
* Make behaviour of cursor.count() on client reflect server
* Change ignoreSkipLimit to applySkipLimit in cursor._getRawObjects
By default cursor._getRawObjects() will set options.applySkipLimit to true, thereby honoring any skip / limit.
cursor.count() on the client now calls _getRawObjects with applySkipLimit set to false by default. See #1202
* Revert default behaviour of cursor.count() to maintain backwards compatibility
This package contains some of the most fragile tests in the entire
codebase, in large part because the author did not account for the
nondeterminism of JS timers across platforms and test runs.
As of React 16, using `ReactDOM.render` in the manner
demonstrated in the `server-render` README will cause a
React deprecation warning. Switching to `ReactDOM.hydrate`
will avoid this. From the React docs:
> Using ReactDOM.render() to hydrate a server-rendered
> container is deprecated and will be removed in React 17.
> Use hydrate() instead.
Source: https://reactjs.org/docs/react-dom.html#render
