During the Meteor 1.6.1 beta period, we introduced logic to render a
<script> tag to load the SockJS library in older browsers (#9353), and so
it seemed important to run test-packages both with and without the
<script> tag, using a special query parameter appended to the app URL.
The #9353 changes were ultimately reverted before Meteor 1.6.1 was
released (see 365804218f), and Meteor 1.6.2
will take a very different approach to bundling dependencies like SockJS
for legacy browsers (#9439). As part of this approach, PhantomJS is always
considered a legacy browser, and as such provides valuable feedback on the
behavior of web.browser.legacy bundles. However, since there's nothing to
configure with regard to SockJS anymore, there's no point in running the
test-packages suite twice in PhantomJS.
In order to run these tests in a modern browser environment, we should
probably revisit the idea of running tests in headless Chrome:
https://github.com/meteor/meteor-feature-requests/issues/254
* Introduce MONGO_BIND_IP override
Introduces an environment variable (MONGO_BIND_IP) for overriding of meteor's mongod's `bind_ip` option to allow docker containers to bind on `0.0.0.0` to be able to expose mongod processs via docker's `-p 3001:3001` port bindings.
Related issue: https://serverfault.com/questions/758225/cannot-connect-to-mongodb-in-docker
Partially Related PR: https://github.com/meteor/meteor/pull/469
* Use METEOR_MONGO_BIND_IP over ambiguous MONGO_BIND_IP
Change request to use METEOR_MONGO_BIND_IP over ambiguous MONGO_BIND_IP
- This changes meteor deploy to poll the /version-status/ REST endpoint
in Galaxy for the build and deploy status of the returned version
- Also fixes up a typo in a test
- Currently only configured to use a default polling configuration
- This change also adds a flag called --no-wait which allows users to
specify that they want the deploy command to behave just as before
This could have prevented #9631 from being a problem in the first place,
and feels like the right thing to do, considering the number of cases
we've seen of people accidentally including babel-preset-meteor in their
.babelrc files.
As usual, we have to bump the ecmascript version as well, so that the
compiler plugin will be rebuilt.
- Bumped patch version number 1.0.0 -> 1.0.1
- ES6 syntax and shorthand applied
- Fixed error in instructions - without the `?close` at the end of the redirect URI, the login popup throws an error
- Bumped patch version number 1.4.0 -> 1.4.1
- ES6 syntax and shorthand applied
- Underscore removed as a dependency
- Globals replaced with module exports
- Adjustment of templates to satisfy several HTML validation warnings in newer versions of Chrome
- Added `autocomplete` attributes to inputs
- Wrapped password-only dialogs forms
- Added hidden `username` and `email` inputs to password-only forms to help with accessibility
- Bumped patch version number 1.5.0 -> 1.5.1
- ES6 syntax and shorthand applied
- Underscore removed as a dependency
- check removed as a client dependency
- Bumped patch version number 1.1.15 -> 1.1.16
- ES6 syntax and shorthand applied
- Underscore and random removed as dependencies
- check removed as a client dependency (it still remains as a server dependency)
