remarkablemark

# set the base image to Debian
# https://hub.docker.com/_/debian/
FROM debian:latest

# replace shell with bash so we can source files
RUN rm /bin/sh && ln -s /bin/bash /bin/sh

# update the repository sources list
# and install dependencies
RUN apt-get update \

forabi

❯ rollup --version
rollup version 0.25.3

❯ time rollup -c ./rollup.js                      
rollup -c ./rollup.js  4.65s user 0.22s system 118% cpu 4.131 total

❯ time webpack                      
Hash: ebb00bbccd954c114d3c
Version: webpack 2.0.7-beta
Time: 3623ms

ryerh

注意：本文内容适用于 Tmux 2.3 及以上的版本，但是绝大部分的特性低版本也都适用，鼠标支持、VI 模式、插件管理在低版本可能会与本文不兼容。

Tmux 快捷键 & 速查表 & 简明教程

启动新会话：

tmux [new -s 会话名 -n 窗口名]

恢复会话：

max-mapper

As a maintainer of native node add-on modules I have some questions about when and why NODE_MODULE_VERSION changes:

(@rvagg has anwered these in the comments below)

• does v8 use semver? how do you know when a v8 version breaks ABI compatibilility?
• is there a semantic meaning for v8 version numbers or is it arbitrary?
• who maintains this google doc I found? is it official?
• why is the latest entry from may in the v8 changelog? https://chromium.googlesource.com/v8/v8.git/+/master/ChangeLog
• how can you tell when all these future v8 versions will be stable? https://chromium.googlesource.com/v8/v8.git/+refs
• why must a node major version correspond to a specific v8 version? e.g. node v5 uses v8 4.6 and won't upgrade to 4.7

Schniz

/** @jsx React.DOM */

var React = require('react');

var handlers = {};
var AsyncRoute = function(req) {
  return React.createClass({
    getInitialState: function() {
      return {
        myComponent: handlers[req]

anvk

/* MIT license
 * 2015 Alexey Novak
 *
 * Inspired by http://youmightnotneedjquery.com/ with few of my own modifications
 *
**/


var deepExtend = function(out) {
  out = out || {};

gaearon

'use strict';

var React = require('react');

function createAsyncHandler(getHandlerAsync, displayName) {
  var Handler = null;

  return React.createClass({
    displayName: displayName,

stephenparish

Commit Message Conventions

These rules are adopted from the AngularJS commit conventions.

• Goals
• Generating CHANGELOG.md
  • Recognizing unimportant commits
  • Provide more information when browsing the history
• Format of the commit message
• Subject line

trevnorris

Notes:

• Text in [[ ]] are the internal libuv function call.
• Text in {{ }} are the Node functions that are affected.
• Text in ( ) are notes about what is happening.
• While the Windows event loop has minor variations, I don't believe any of those affect Node.

---

On process.nextTick():

guweigang

git init                                                  # 初始化本地git仓库（创建新仓库）
git config --global user.name "xxx"                       # 配置用户名
git config --global user.email "xxx@xxx.com"              # 配置邮件
git config --global color.ui true                         # git status等命令自动着色
git config --global color.status auto
git config --global color.diff auto
git config --global color.branch auto
git config --global color.interactive auto
git config --global --unset http.proxy                    # remove  proxy configuration on git
git clone git+ssh://git@192.168.53.168/VT.git             # clone远程仓库