HTTPS clone URL
Subversion checkout URL
- Accessing Meteor provided build machines from Windows
- Blaze Community Guidelines
- Breaking changes in Meteor 1.2
- Build Machines
- Build Plugins API
- Building cross platform packages for Meteor
- CompileStep API for Build Plugin Source Handlers
- Configuring Twitter in Local Market
- Contributing to Meteor
- Contributor Guidelines
- Cordova Installation: Android on Linux
- Cordova Installation: Android on Mac
- Cordova Installation: iOS on Mac
- Facebook Graph API Upgrade
- File Change Watcher Efficiency
- GitHub Issue Labels
- How to run your app on an Android device
- How to run your app on an iOS device
- How to submit your Android app to Play Store
- How to submit your iOS app to App Store
- Isobuild Feature Packages
- Meteor Cordova integration
- Meteor Cordova Phonegap integration
- Meteor on Windows: Alternate installation
- Meteor Package Server API
- Meteor Style Guide
- Mobile Dev Install: Android on Linux
- Mobile Dev Install: Android on Mac
- Mobile Dev Install: iOS on Mac
- Mobile Development Install: Android on Linux
- Mobile Development Install: Android on Mac
- Mobile Development Install: iOS on Mac
- New Template Engine Preview
- OAuth for mobile Meteor clients
- Oplog Observe Driver
- Preview of Meteor on Windows
- Publishing a package with binary dependencies for the Windows preview
- React components must be the only thing in their wrapper element
- Supported Platforms
- Tools for a simple development environment for Meteor on Windows
- Tracker Manual
- Using Blaze
- Using Meteor behind a proxy
- Build machines
- Build Plugins API
- CompileStep API for build plugins
- File change watcher efficiency
- Package server API
- Oplog observe driver
- Tracker manual
Clone this wiki locally
Visit Stackoverflow.com, or the IRC channel(freenode.com).
The best way (the only way?) to contribute code is to submit a pull request. We have a few guidelines for you.
- Development happens on the devel branch, so please make sure your branch is based off that.
- Sign the contributor's agreement.
- Follow the Meteor style guide.
- Limit yourself to one feature or bug fix per pull request.
- Name your branch to match the feature/bug fix that you are submitting.
- Write clear, descriptive commit messages.
We love new pre-processor packages. Here are some guidelines for submitting a new pre-processor:
It should have tests. See
It should be documented. See
It should be a stable version. If it requires an npm module install, make sure to add it to
admin/generate-dev-bundle.shwith a fixed version number. If the preprocessor is only a few files, you can avoid the dev bundle and simply put the code in the package directory.
Because the package API is still in flux, and because there are so many client-side libraries out there, we're not taking new packages that only include files to be shipped to the client at this time. You can easily get the same effect by placing the files in your application source tree. Place client library files in the directory
If you're working on a big ticket item, best to check in first on the #meteor IRC channel or email us at email@example.com. We'd hate to have to steer you in a different direction after you've already put in a lot of hard work.