samuel-alves

Directory structure for JavaScript/Node Projects

While the following structure is not an absolute requirement or enforced by the tools, it is a recommendation based on what the JavaScript and in particular Node community at large have been following by convention.

Beyond a suggested structure, no tooling recommendations, or sub-module structure is outlined here.

Directories

lib/ is intended for code that can run as-is
src/ is intended for code that needs to be manipulated before it can be used

1. Clone your fork:

git clone git@github.com:YOUR-USERNAME/YOUR-FORKED-REPO.git

2. Add remote from original repository in your forked repository:

cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream

Here's how you could create custom error classes in Node.js using latest ES6 / ES2015 syntax.

I've tried to make it as lean and unobtrusive as possible.

Defining our own base class for errors

errors/AppError.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');

	<script type="text/javascript">

	// Case Data preparation
	var postData = {
	oid: '00D0b000000xxxx', //Put your ORGID here
	name:'John Smith',
	company:'ACME',
	email:'yyy@customercompany.com',
	origin:'Web',
	subject:'Web2Case using the custom API',

-DELETE relations.*, taxes.*, terms.*
-FROM wp_term_relationships AS relations
-INNER JOIN wp_term_taxonomy AS taxes
-ON relations.term_taxonomy_id=taxes.term_taxonomy_id
-INNER JOIN wp_terms AS terms
-ON taxes.term_id=terms.term_id
-WHERE object_id IN (SELECT ID FROM wp_posts WHERE post_type='product');
-DELETE FROM wp_postmeta WHERE post_id IN (SELECT ID FROM wp_posts WHERE post_type = 'product');
-DELETE FROM wp_posts WHERE post_type = 'product';

	#!/bin/bash

	# Source: http://blog.nonuby.com/blog/2012/07/05/copying-env-vars-from-one-heroku-app-to-another/

	set -e

	sourceApp="$1"
	targetApp="$2"

	while read key value; do

	var parser = document.createElement('a');
	parser.href = "http://example.com:3000/pathname/?search=test#hash";

	parser.protocol; // => "http:"
	parser.hostname; // => "example.com"
	parser.port; // => "3000"
	parser.pathname; // => "/pathname/"
	parser.search; // => "?search=test"
	parser.hash; // => "#hash"
	parser.host; // => "example.com:3000"

	var myScript = document.createElement('script');
	myScript.src = 'http://code.jquery.com/jquery-2.1.4.min.js';
	myScript.onload = function() {
	console.log('jQuery loaded.');
	};

	document.body.appendChild(myScript);