tcbyrd

{
  "version": 2,
  "builds": [
    { "src": "probot.js", "use": "@now/node" }
  ],
  "env": {
    "GITHUB_TOKEN": "@github-token",
    "APP_ID": "@app-id",
    "PRIVATE_KEY": "@private-key-base64"
  },

roelvan

require('dotenv').config();

const http = require('http');
const url = require('url');
// import NOW SETTINGS
const now = require('./now.json');

const PORT = process.env.PORT || 3030;

const routes = now.routes.reduce((map, route) => {

aweary

import React from "react";
import useMutableReducer from "./useMutableReducer";

const reducer = (draft, action, state) => {
  switch (action) {
    case "increment":
      draft.count++;
      break;
    case "decrement":
      draft.count--;

naesheim

##################
### config.yml ###
##################

version: 2
jobs:
    build:
        docker:
            - image: circleci/python:3.6
        steps:

clhenrick

WITH
-- write the new values
n(ip,visits,clicks) AS (
  VALUES ('192.168.1.1',2,12),
         ('192.168.1.2',6,18),
         ('192.168.1.3',3,4)
),
-- update existing rows
upsert AS (
  UPDATE page_views o

jfmengels

lodash v4.17.20

Array

• _.chunk
• _.compact
• _.concat

n0ts

# http://stackoverflow.com/questions/5735666/execute-bash-script-from-url
bash <(curl -s http://mywebsite.com/myscript.txt)

# http://stackoverflow.com/questions/4642915/passing-parameters-to-bash-when-executing-a-script-fetched-by-curl
curl http://foo.com/script.sh | bash -s arg1 arg2

branneman

Better local require() paths for Node.js

Problem

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.

Possible solutions