In addition to the Storybook for React setup, you'll also need to install these packages:
npm i -D @babel/core babel-loader css-loader style-loader
In addition to the Storybook for React setup, you'll also need to install these packages:
npm i -D @babel/core babel-loader css-loader style-loader
This is a guide for aligning images.
See the full Advanced Markdown doc for more tips and tricks
By: @BTroncone
Also check out my lesson @ngrx/store in 10 minutes on egghead.io!
Update: Non-middleware examples have been updated to ngrx/store v2. More coming soon!
Table of Contents
modules.export = (function(){ | |
var Promise = require('bluebird'); | |
var fs = Promise.promisifyAll(require('fs')); | |
return function(params, cb) { | |
return fs.doSomeStuffAsync(params) | |
.then(function(result){ | |
return someOtherAsync(result); | |
}) | |
.then(function(moreResults){ | |
return someMoreAsync(moreResults); |
## Build generated | |
build/ | |
DerivedData | |
build.xcarchive | |
## Various settings | |
*.pbxuser | |
!default.pbxuser | |
*.mode1v3 | |
!default.mode1v3 |
This guide assumes that you recently run brew upgrade postgresql
and discovered to your dismay that you accidentally bumped from one major version to another: say 9.3.x to 9.4.x. Yes, that is a major version bump in PG land.
First let's check something.
brew info postgresql
The top of what gets printed as a result is the most important:
// Overlays one color on top of another and returns the resulting color. | |
// This is used to determine contrast ratio for two colors with partial opacity. | |
// See http://en.wikipedia.org/wiki/Alpha_compositing#Alpha_blending | |
@function alpha-blend($overlay, $base) { | |
$overlayAlpha: alpha($overlay); | |
$baseAlpha: alpha($base); | |
// If the overlaid color is completely opaque, then the result is just going to be that color. | |
@if $overlayAlpha >= 1 { | |
@return $overlay; |
var nconf = require('nconf'); | |
var yaml = require('js-yaml'); | |
var app_config = __dirname + '../config/application.yml'; | |
// load cmd line args and environment vars | |
nconf.argv().env(); | |
// load a yaml file using a custom formatter | |
nconf.file({ |
It is easy to get service accounts working with App Engine's app_devserver.py
- once you know how.
On the way there, you might have pulled out all your hair following one documentation dead end after another, trying to piece together the right information.
Here are the steps you need to take, in exact order, to get this working. Once you follow these steps, you'll be able to use service accounts in local development, so that you can interact with Google APIs (e.g.: Spreadsheet, Calendar) in a way that is consistent with the deployment environment on App Engine.
In order to follow the instructions, you'll be better off using the latest UI for Google Cloud projects. Older interfaces (such as the dedicated App Engine dashboard) have things in different places, under different names, etc. It is a world of pain there.
Also note that I've tested this on several 1.9.x releases of App Engine; I can't confirm the behaviour of earlier releases.