- Install XCode from App Store.
- Open XCode and agree to terms and conditions.
xcode-select --install
| "use strict"; | |
| // Use | |
| // var React = require('./react'); | |
| // instead if you are loading React externally, via a <script> element | |
| var React = require('react'); | |
| var App = React.createClass({ | |
| render: function() { | |
| return <h3>Hello World!</h3>; |
| # Hello, and welcome to makefile basics. | |
| # | |
| # You will learn why `make` is so great, and why, despite its "weird" syntax, | |
| # it is actually a highly expressive, efficient, and powerful way to build | |
| # programs. | |
| # | |
| # Once you're done here, go to | |
| # http://www.gnu.org/software/make/manual/make.html | |
| # to learn SOOOO much more. |
| /** | |
| * Destroy the user's session (logout). | |
| * | |
| * @return Response | |
| */ | |
| public function destroy() | |
| { | |
| Auth::logout(); | |
| flash()->info('You are now logged out.'); |
| var gulp = require('gulp'); | |
| var sourcemaps = require('gulp-sourcemaps'); | |
| var source = require('vinyl-source-stream'); | |
| var buffer = require('vinyl-buffer'); | |
| var browserify = require('browserify'); | |
| var watchify = require('watchify'); | |
| var babel = require('babelify'); | |
| function compile(watch) { | |
| var bundler = watchify(browserify('./src/index.js', { debug: true }).transform(babel)); |
Droplr will auto-copy the sharing link when you take a screenshot. You'll use this on GitHub.
That copied link will look like this: http://d.pr/i/13PDt
To paste that into a GitHub issue:

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent| // Dagger 1 example | |
| @Module( | |
| complete = false, | |
| library = true | |
| ) | |
| public final class ApiModule { | |
| @Provides | |
| @Singleton | |
| Retrofit provideRetrofit(Gson gson, Application app) { | |
| return new Retrofit.Builder() |
| import { Component, PropTypes } from 'react' | |
| import { noop } from 'lodash' | |
| import raf from 'raf' | |
| const cache = new Map() | |
| export function createNonBlockingRenderLoop({ key, concurrencyLevel = 1 }) { | |
| if (cache.has(key)) { | |
| return cache.get(key) | |
| } |
You probably arrived here because of a curt message in response to an issue you filed on a repo that I contribute to. Sorry about that (particularly if you filed the issue long ago and have been waiting patiently for a response). Let me explain:
I work on a lot of different open source projects. I really do like building software that makes other people's lives easier, but it's crazy time-consuming. One of the most time-consuming parts is responding to issues. A lot of OSS maintainers will bend over backwards to try and understand your specific problem and diagnose it, to the point of setting up new test projects, fussing around with different Node versions, reading the documentation for build tools that we don't use, debugging problems in third party dependencies that appear to be involved in the problem... and so on. I've personally spent hundreds of hours of my free time doing these sorts of things to try and help people out, because I want to be a responsible maintainer and I