vaibhavdshinde

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:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

Summary notes for lecture of course cs1911 - UNSW

Week 1

Assessment

Tutorial and Lab work - 10%

Jitbit's SQL interview questions

http://www.jitbit.com/news/181-jitbits-sql-interview-questions/

Schema

employees

employee_id
department_id
boss_id
name

MongoDB Practice

MongoDB Exercise in mongo shell

create database

Connect to a running mongo instance, use a database named mongo_practice. use mongo_practice

Insert Documents

Interview Questions

MongoDB

Q1: Explain what is MongoDB? ☆

Answer: MongoDB is an open-source document database that provides high performance, high availability, and automatic scaling. It's Key Features are:

Document Oriented and NoSQL database.

MongoDB Practice

MongoDB Exercise in mongo shell

Connect to a running mongo instance, use a database named mongo_practice.

Document all your queries in a javascript file to use as a reference.

Insert Documents

A quick overview of the node.js streams interface with basic examples.

This is based on @brycebaril's presentation, Node.js Streams2 Demystified

Overview

Streams are a first-class construct in Node.js for handling data.

Think of them as as lazy evaluation applied to data.

	// List all files in a directory in Node.js recursively in a synchronous fashion
	var walkSync = function(dir, filelist) {
	var fs = fs \|\| require('fs'),
	files = fs.readdirSync(dir);
	filelist = filelist \|\| [];
	files.forEach(function(file) {
	if (fs.statSync(dir + file).isDirectory()) {
	filelist = walkSync(dir + file + '/', filelist);
	}
	else {