rjyo/yaml-config-node — pull request #2 by chakrit (2012-09-08 20:43:47+00:00)
Title: Use nodeca/js-yaml instead of visionmedia/js-yaml

**visionmedia/js-yaml:**

* It has [lots of unresolved open issues](https://github.com/visionmedia/js-yaml/issues) with regards to parsing errors with some from 10 months ago.
* This results in a lot of parsing error for the most basic YAML usage. Which totally sucked.
* Last commit is [9 months ago](https://github.com/visionmedia/js-yaml/branches)

**nodeca/js-yaml:**

* It has much much better YAML support ironically. (esp. for YAML 1.1)
* It has lots of [tests](https://github.com/nodeca/js-yaml/tree/master/test)
* It has close amount of Github stars :)

**Example document taht fails with visionmedia/js-yaml**

---
default:
server:
cookieSecret: 'numbers.in.th'
port: 8888
log:
verbose: false
colorize: true
db:
path: ./db
names:
- 'thailand'
users:
- username: 'admin'
password: 'admin'
- username: 'test'
password: 'test'

As you can see, the document is very basic yet `visionmedia/js-yaml` fails to parse it correctly.

So please switch the yaml module. It seriously sucked.