In testing for #7715, I discovered that the v2.2 Graph API endpoint was still in use in the `facebook` package which was due to sunset on 2017-03-25. See Facebook Graph API Changelog here: https://developers.facebook.com/docs/apps/changelog When a Graph API endpoint is sunset, it (is claimed) to automatically turn over to the next more recent version, in this case v2.3. v2.3 has a breaking-change over v2.2, notably listed in "Changes from v2.2 to v2.3": > [Oauth Access Token] Format - The response format of https://www.facebook.com/v2.3/oauth/access_token returned when you exchange a code for an access_token now return valid JSON instead of being URL encoded. The new format of this response is {"access_token": {TOKEN}, "token_type":{TYPE}, "expires_in":{TIME}}. We made this update to be compliant with section 5.1 of RFC 6749. This change updates both Graph APIs to v2.8 which has LTS until "At least October 2018".
Meteor
Meteor is an ultra-simple environment for building modern web applications.
With Meteor you write apps:
- in pure JavaScript
- that send data over the wire, rather than HTML
- using your choice of popular open-source libraries
Try the getting started tutorial.
Next, read the guide or the reference documentation at http://docs.meteor.com/.
Quick Start
On Windows, simply go to https://www.meteor.com/install and use the Windows installer.
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
Slow Start (for developers)
If you want to run on the bleeding edge, or help contribute to Meteor, you can run Meteor directly from a Git checkout using these steps:
-
Clone from GitHub
$ git clone --recursive https://github.com/meteor/meteor.git $ cd meteorImportant note about Git submodules!
This repository uses Git submodules. If you clone without the
--recursiveflag, re-fetch withgit pullor experience "Depending on unknown package" errors, run the following in the repository root to sync things up again:$ git submodule update --init --recursive -
(Optional) Compile dependencies
This optional step requires a C and C++ compiler, autotools, and scons. If this step is skipped, Meteor will simply download pre-built binaries.
To build everything from scratch (
node,npm,mongodb, etc.) run the following:$ ./scripts/generate-dev-bundle.sh # OPTIONAL! -
Run a Meteor command to install dependencies
If you did not compile dependencies above, this will also download the binaries.
$ ./meteor --help -
Ready to Go!
Your local Meteor checkout is now ready to use! You can use this
./meteoranywhere you would normally call the systemmeteor. For example,:$ cd my-app/ $ /path/to/meteor-checkout/meteor runNote: When running from a
gitcheckout, you cannot pin apps to specific Meteor releases or change the release using--release.
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.
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 contributing to Meteor?
- Issue tracker: https://github.com/meteor/meteor/issues
- Contribution guidelines: https://github.com/meteor/meteor/tree/devel/Contributing.md
We are hiring! Visit https://www.meteor.com/jobs to learn more about working full-time on the Meteor project.