anildigital

docker rmi $(docker images -q -f dangling=true)

arqex

/*
 * Your Stylesheet
 *
 * This stylesheet is loaded when Atom starts up and is reloaded automatically
 * when it is changed.
 *
 * If you are unfamiliar with LESS, you can read more about it here:
 * http://www.lesscss.org
 *
 * To apply this styles to your editor click on 

nmerouze

package main

import (
	"encoding/json"
	"log"
	"net/http"
	"reflect"
	"time"

	"github.com/gorilla/context"

yvele

# Version key/value should be on his own line
PACKAGE_VERSION=$(cat package.json \
  | grep version \
  | head -1 \
  | awk -F: '{ print $2 }' \
  | sed 's/[",]//g' \
  | tr -d '[[:space:]]')

echo $PACKAGE_VERSION

DarrenN

# Version key/value should be on his own line
PACKAGE_VERSION=$(cat package.json \
  | grep version \
  | head -1 \
  | awk -F: '{ print $2 }' \
  | sed 's/[",]//g')

echo $PACKAGE_VERSION

cantidio

HOW to CREATE a commit using github API

1. Get the Reference of the branch you want to commit to and store the SHA for the latest commit (SHA-LATEST-COMMIT)

https://developer.github.com/v3/git/refs/#get-a-reference

  const res = getReference( BRANCH );
  const baseCommitSHA = res.object.sha;

2. Get the sha of the tree

https://developer.github.com/v3/git/commits/#get-a-commit

mcarrowd

package main

import (
	"fmt"
	"golang.org/x/text/encoding/charmap"
)

func main() {
	for i := 0; i <= 255; i++ {
		charnum := uint8(i)

rauchg

Minimum Viable Async with Node 6

With the release of Node 6.0.0, the surface of code that needs transpilation to use ES6 features has been reduced very dramatically.

This is what my current workflow looks like to set up a minimalistic and fast microservice using micro and async + await.

The promise

alekseykulikov

Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.

My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important). During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.

Here are main principles we use to write CSS for modern (IE11+) browsers:

• SUIT CSS naming conventions + SUIT CSS design principles;
• PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
• Flexbox is awesome. No need for grid framework;
• Normalize.css, base styles and variables are solid foundation for all components;

maxclaus

# Simple version using only "find"
find . -name "node_modules" -type d -prune -exec rm -rf '{}' +