obonyojimmy

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

obonyojimmy

module MyModule {
    export class MyClass extends Vue {

        // define instance methods
        myMethod() {
            // the TS-Type of "this" is defined as Instance of MyClass
            console.log("myMethod");
        }
        myOtherMethod() {
            console.log("myOtherMethod");

obonyojimmy

<?php namespace App\Http\Controllers\Api\V1;

use App\Http\Controllers\Controller;
use App\Http\Requests;
use Illuminate\Http\Request;
use Tymon\JWTAuth\Facades\JWTAuth;
use Tymon\JWTAuth\Exceptions\JWTException;

class AuthenticateController extends Controller
{

obonyojimmy

package main

import (
	"fmt"
	"io"
	"os"
)

var path = "/Users/novalagung/Documents/temp/test.txt"

obonyojimmy

package main

import (
	"fmt"
	"syscall"
	"time"
	"unsafe"
)

func main() {

obonyojimmy

package main

import (
	"log"
	"syscall"
	"unsafe"
)

var (
	kernel32 = syscall.NewLazyDLL("kernel32.dll")

obonyojimmy

package main

import (
	"fmt"
	"io"
	"log"
	"io/ioutil"
	"time"
	"golang.org/x/sys/windows"
)

obonyojimmy

/**
 * Copyright (c) 2006, Nicolas Hillegeer
 * All rights reserved.
 * 
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions are met:
 *     * Redistributions of source code must retain the above copyright
 *       notice, this list of conditions and the following disclaimer.
 *     * Redistributions in binary form must reproduce the above copyright
 *       notice, this list of conditions and the following disclaimer in the

obonyojimmy

First, you create your branch locally:

git checkout -b

The remote branch is automatically created when you push it to the remote server. So when you feel ready for it, you can just do:

git push

Where is typically origin, the name which git gives to the remote you cloned from. Your colleagues would then just pull that branch, and it's automatically created locally.

obonyojimmy

// Copyright 2015 <chaishushan{AT}gmail.com>. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.

// +build ingore

package main

import (
	"flag"