This sentence is about ECV but nothing else in the docs discusses ECV
and it doesn't use that term. So it's actually kind of confusing; to me,
it suggested that asking for `1.2.3_1` might give you `1.2.3`, which is
not true.
Old:
$ curmeteor add iron:router@9.9.9
Got error during resolve; trying refresh { [Error: conflict: constraints on iron:router cannot be satisfied.
Constraints come from:
<top level>] constraintSolverError: true }
Could not satisfy all the specified constraints:
Error: conflict: constraints on iron:router cannot be satisfied.
Constraints come from:
<top level>
New:
$ curmeteor add iron:router@9.9.9
iron:router@9.9.9: no such version
We started calling our releases 0.9.3.1-rc.0 to match what you need to
do in semver to get proper numeric comparisons; let's make sure to
create orderKeys that work with them.
Clean up on every soft restart (every time the js app loads) not on every hard
restart (every time the native shell loads). This fixes the problem described
in issue #2727: HCP cache keeps accumulating in development mode leading to
crashes.
The server sends hot code push updates to mobile clients with ROOT_URL
and DDP_DEFAULT_CONNECTION_URL taken from the MOBILE_ROOT_URL and
MOBILE_DDP_URL environment variables. These are set by the main meteor
process when it starts the app runner.
* --port now requires a port ('meteor run --port example.com' isn't valid).
* --mobile-server defaults to your detected IP address and the port from
--port.
* If you provide a value for --mobile-server, we default to http:// as
the protocol. A host is required for --mobile-server if you don't omit
the option entirely. Similar for the --server argument to 'meteor
build'.
This commit includes the 'netroute' npm module as a core package (which
has binary dependencies) for IP detection. It would be nice to put it in
packages/non-core, but I think it has to be a core package in order to
uniload it.
