- Hubot であそぼう
#!/bin/bash | |
set -o pipefail | |
set -e | |
HASH=$(git log --oneline | peco | cut -d " " -f 1) | |
if [ "$?" -ne 0 -o -z "$HASH" ]; then | |
exit 1 | |
fi | |
git commit --fixup "$HASH" $@ | |
# install: |
--log_gc (Log heap samples on garbage collection for the hp2ps tool.) | |
type: bool default: false | |
--expose_gc (expose gc extension) | |
type: bool default: false | |
--max_new_space_size (max size of the new generation (in kBytes)) | |
type: int default: 0 | |
--max_old_space_size (max size of the old generation (in Mbytes)) | |
type: int default: 0 | |
--max_executable_size (max size of executable memory (in Mbytes)) | |
type: int default: 0 |
/** | |
* Track JS error details in Universal Analytics | |
*/ | |
function trackJavaScriptError(e) { | |
var errMsg = e.message; | |
var errSrc = e.filename + ': ' + e.lineno; | |
ga('send', 'event', 'JavaScript Error', errMsg, errSrc, { 'nonInteraction': 1 }); | |
} | |
curl --header 'Authorization: token INSERTACCESSTOKENHERE' \ | |
--header 'Accept: application/vnd.github.v3.raw' \ | |
--remote-name \ | |
--location https://api.github.com/repos/owner/repo/contents/path | |
# Example... | |
TOKEN="INSERTACCESSTOKENHERE" | |
OWNER="BBC-News" | |
REPO="responsive-news" |
Yet another framework syndrome
Name | Date | URL | Stars |
---|---|---|---|
Jake | April 2010 | https://github.com/mde/jake | 1000 |
Brunch | January 2011 | http://brunch.io/ | 3882 |
フロントエンドデベロッパ/エンジニアの定義は様々です。しかし現在のWeb開発において欠かすことができない能力の1つであることは間違いありません。
フロントエンドを専門とする人は決して多くはありませんが、誰しもが少しのフロントエンドの経験を持っているはずです。その経験を次のレベルに上げていくために知っておきたい、現在のフロントエンドデベロッパに求められるスキルセットについて紹介していきます。
Sass 3.3 is coming soon, and along with it several major new features. It supports source maps, SassScript maps, and the use of &
in SassScript. In preparation for its release, we've put out a couple of release candidates to be sure that everything was set and ready to go. Unfortunately, it wasn't.
Release candidates often turn up small bugs and inconsistencies in new features, but it's rare that they find anything truly damning. In this case, though, several users noticed an issue with using &
in SassScript that rendered a sizable chunk of our plan for that section of 3.3 unworkable. It's not a fatal issue, and we think we have a good plan for dealing with it (I'll get to that in a bit), but it is a problem.
To understand what's wrong, first you need to understand the reason we decided to make &
accessible to SassScript in the first place. One thing users want to do pretty often is to add suffixes to classes. Sometimes this takes the place of nest
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');
Those suck for maintenance and they're ugly.