Skip to content

Instantly share code, notes, and snippets.

# Logs
logs
*.log
# Runtime data
pids
*.pid
*.seed
# Directory for instrumented libs generated by jscoverage/JSCover
const express = require('express')
const app = new express()
const router = express.Router()
const pathToRegexp = require('path-to-regexp')
const permission = () => (req, res, next) => {
const config = {
class State {
approve() {
throw 'Should override this function'
}
reject() {
throw 'Should override this function'
}
}
class Verifying extends State {
Axure RP 7.0注册码
用户名:axureuser
序列号:8wFfIX7a8hHq6yAy6T8zCz5R0NBKeVxo9IKu+kgKh79FL6IyPD6lK7G6+tqEV4LG
const 404 = 'Page Not Found'
const portfolio = [
{
name: "Facebook messenger bot using AWS Lamba and API Gateway",
url: "https://www.facebook.com/events/724852200951265/",
repo: "https://github.com/goodideas-studio/facebook-messenger-bot-using-aws"
}, {
name: "uni-order-no",
description: "Unique order no generator",
repo: "https://github.com/jacky810124/uni-order-no"
}, {
const JackyHuang = {
username: "Jacky Huang",
gender: "Male",
birthday: "1992-01-24",
skill: {
front_end: ['HTML', 'CSS', 'JavaScript', 'jQuery', 'SASS', 'Bootstrap', 'Vue', 'React', 'ES6', 'RWD', 'Redux'],
back_end: ['NodeJS', 'Express', 'Mocha'],
experiences: [
'Familiar with git version control',
@jacky810124
jacky810124 / better-nodejs-require-paths.md
Created August 25, 2016 20:43 — forked from branneman/better-nodejs-require-paths.md
Better local require() paths for Node.js

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:

var Article = require('../../../models/article');

Those suck for maintenance and they're ugly.

Possible solutions

We couldn’t find that file to show.
function Post() {
//example 1
this.getTen = function(){}
}
//example 2
Post.prototype.getTen = function(){}
//example 3