Create and initialize your a directory for your Express application.
$ mkdir node-knex-demo
$ cd node-knex-demo
$ npm init
// This code demonstrates a simplified "stackification" algorithm to turn | |
// instructions in a basic block back into a tree. This is useful when | |
// generating WebAssembly code from assembly instructions in SSA form. | |
// | |
// It's the algorithm used by LLVM's WebAssembly backend, viewable here: | |
// https://github.com/llvm-mirror/llvm/blob/master/lib/Target/WebAssembly/WebAssemblyRegStackify.cpp | |
type InsKind = | |
'Add' | | |
'LocalSet' | |
'use strict'; | |
const crypto = require('crypto'); | |
const ENC_KEY = "bf3c199c2470cb477d907b1e0917c17b"; // set random encryption key | |
const IV = "5183666c72eec9e4"; // set random initialisation vector | |
// ENC_KEY and IV can be generated as crypto.randomBytes(32).toString('hex'); | |
const phrase = "who let the dogs out"; | |
var encrypt = ((val) => { |
This document is written to help JavaScript developers to understand JavaScript's weird parts deeply and to prepare for interviews, the following resources was really helpful to write this document:
image: node:7.4 | |
# Yes, you do need this in order to be able to do onward pushes. | |
clone: | |
depth: full | |
pipelines: | |
default: | |
# Don't forget caches as well. | |
- step: |
If you have been a web developer for a while, you probably feel like you're going in circles. Going all the way back to CGI scripts, you were generating HTML using string literals, formatting and concatenation:
const message = "Hello, World!!!"
console.log("<html><body>" + message + "</body></html>");
Then someone decided it would be easier to inline code into HTML documents directly, using a more declarative approach:
This cheat sheet provides a detailed overview of the exposed lifecycle events and available commands (and entrypoints) of the Serverless framework, that can be hooked by plugins (internal and external ones). The document is structured by the commands invoked by the user.
Lifecycle events are shown as the globally available outer events (all providers) and sub lifecycle events that are provider specific in the called order. Currently only the AWS provider is shown. If you have information about the other provider,
package main | |
import( | |
"fmt" | |
"log" | |
"encoding/json" | |
"net/http" | |
"os" | |
"github.com/stripe/stripe-go/client" | |
"github.com/stripe/stripe-go" |
I no personal preference/order
vim-elixir: Vim configuration files for Elixir
Janus: This is a distribution of plug-ins and mappings for Vim, Gvim and MacVim.