Real unit test (isolation, no children render)
Calls:
- constructor
- render
<html> | |
<head> | |
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script> | |
<script> | |
function submitToAPI() { | |
var URL = ‘/contact’; | |
var data = { | |
name: $(‘#name-input’).val(), | |
email: $(‘#email-input’).val(), | |
description: $(‘#description-input’).val() |
#!/usr/bin/env node | |
console.log('\x1b[1m','Please wait for linting to run...','\x1b[0m'); | |
console.log('You can','\x1b[1m','skip','\x1b[0m','the precommit hook by running "git commit -n" instead','\x1b[1m', "but beware!",'\x1b[0m'); | |
require('child_process').exec( | |
'make verify', | |
function (error, stdout) { | |
console.log(stdout && 'stdout: ' + stdout); | |
if (error !== null) { |
# The initial version | |
if [ ! -f .env ] | |
then | |
export $(cat .env | xargs) | |
fi | |
# My favorite from the comments. Thanks @richarddewit & others! | |
set -a && source .env && set +a |
find `pwd` -type d -maxdepth 3 -name 'node_modules' | xargs -n 1 tmutil addexclusion |
# Makefile for transpiling with Babel in a Node app, or in a client- or | |
# server-side shared library. | |
.PHONY: all clean | |
# Install `babel-cli` in a project to get the transpiler. | |
babel := node_modules/.bin/babel | |
# Identify modules to be transpiled by recursively searching the `src/` | |
# directory. |
#!/bin/bash | |
target_branch="production" | |
working_tree="PATH_TO_DEPLOY" | |
while read oldrev newrev refname | |
do | |
branch=$(git rev-parse --symbolic --abbrev-ref $refname) | |
if [ -n "$branch" ] && [ "$target_branch" == "$branch" ]; then | |
⚡ See me talk about this at the London Node User Group ⚡
Found out today that while debugging a node application using console.log()
in the terminal I can pass arguments that formats the styles in the console.
console.log('\x1b[31m', 'Hello, world', '\x1b[0m'); // red
I really liked @tjvantoll article Handling Failed HTTP Responses With fetch(). The one thing I found annoying with it, though, is that response.statusText
always returns the generic error message associated with the error code. Most APIs, however, will generally return some kind of useful, more human friendly message in the body.
Here's a modification that will capture this message. The key is that rather than throwing an error, you just throw the response and then process it in the catch
block to extract the message in the body:
fetch("/api/foo")
.then( response => {
if (!response.ok) { throw response }
return response.json() //we only get here if there is no error
})
/* | |
A neuron is basically the sum of its synapses. | |
Along with a trigger threshold, that's all we need to calculate | |
whether or not it will trigger at any given moment: | |
*/ | |
const neuron = ({ synapses = [], threshold = 1 } = {}) => ({ | |
synapses, | |
threshold | |
}); |