mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
fe9e4035f9
Now that we're postponing the legacy build until after the first client refresh message is sent, there's a risk that changes to the legacy build will not be picked up until after the next rebuild. If we attempted to fix that problem by sending the refresh message after the legacy bundle is rebuilt, then we would lose most of the benefit of delaying the legacy build, because the client would not refresh until after the legacy build completed. The right way to fix the problem is by sending a second client refresh message after the legacy build finishes, but doing so with the current autoupdate implementation would very likely cause modern clients to reload a second time. The solution implemented by this commit is simple in theory: the autoupdate package should keep track of distinct versions for each client architecture, so that modern clients will refresh only when the modern versions change, and legacy clients will refresh only when the legacy versions change, which allows us to send two refresh messages without causing any clients to refresh more than once. In reality, this was a fairly major rewrite, since the ClientVersions collection has a totally different schema now. I've tested it as well as I can, though I'm not entirely sure what will happen if clients using the previous version of the autoupdate package begin receiving DDP messages from this version of the autoupdate server code.
Meteor is an ultra-simple environment for building modern web applications.
With Meteor you write apps:
- in modern JavaScript
- that send data over the wire, rather than HTML
- using your choice of popular open-source libraries
Try a getting started tutorial:
Next, read the guide and the documentation.
Quick Start
On Windows, the installer can be found at https://www.meteor.com/install.
On Linux/macOS, use this line:
curl https://install.meteor.com/ | sh
Create a project:
meteor create try-meteor
Run it:
cd try-meteor
meteor
Developer Resources
Building an application with Meteor?
- Announcement list: sign up at http://www.meteor.com/
- Having problems? Ask for help at: http://stackoverflow.com/questions/tagged/meteor
- Discussion forums: https://forums.meteor.com/
Interested in helping or contributing to Meteor? These resources will help:
We are hiring! Visit meteor.io/jobs to learn more about working full-time on the Meteor project.
Uninstalling Meteor
Aside from a short launcher shell script, Meteor installs itself inside your home directory. To uninstall Meteor, run:
rm -rf ~/.meteor/
sudo rm /usr/local/bin/meteor
On Windows, just run the uninstaller from your Control Panel.