Great little utility. Went to feed it a yaml stream on stdin from a bash unix pipe and noticed not setup to read stdin. Did I miss something? If not, would you mind if I setup a pull request to add that functionality? (I'll wait to start the work to hear back to know if that is something you already intended or I missed.)

Brings up a bigger question about any standards or best practices for creating node command line utilities in general. Some commands take -- to indicate stdin coming and others just deal with it if there is something on the stdin pipe to read from.

Hi,

I am using yaml2json for the first time. My OS is Windows 7 and I am using git bash.
May be I am missing something very basic, can you guys please help/guide me here.

I tried sending the output of the bash text processing command to test.yml and I can see the test.yml file is created properly. But once I feed it as a input to yaml2json, it parses just the first line "version" :1 and exits without any error.

However, If I try to convert test.yml file contents online via site:--http://yamltojson.com/-- the resulting .json is proper.

Following are the contents of test.yml file generated:--

version: 1
layout: post
lang: en
slug: "checklist"
type: "modal"
title: "Checklist"
published: "true"
categories: "mobile"
tags: "mobile"
action:

• title: "Disguise Now"
  link: "close"
• title: "Cancel"
  link: "home-ready"
  status: disabled
  checklist:
• title: "Review security plan and update contacts regularly"
• title: "Test the alert to ensure it is working"
• title: "Ensure sufficient credit on the phone"
• title: "Activate GPS (if you want to enable location tracking)"
• title: "Charge phone battery to full"

echo '{"gti-dev":{"description":"development environment"},"virtualization":"HyperV","host OS":"ESXi"}' | json2yaml | yaml2json
/usr/local/lib/node_modules/yaml2json/node_modules/yaml/lib/yaml.js:179
throw new Error(msg + ', ' + context(this.peek()[1].input))
^

Error: document not properly dedented, near "host OS: "ESXi"\n\n"
at Parser.expect (/usr/local/lib/node_modules/yaml2json/node_modules/yaml/lib/yaml.js:179:9)
at Parser.parseDoc (/usr/local/lib/node_modules/yaml2json/node_modules/yaml/lib/yaml.js:266:8)
at Parser.parse (/usr/local/lib/node_modules/yaml2json/node_modules/yaml/lib/yaml.js:232:19)
at Object.exports.eval (/usr/local/lib/node_modules/yaml2json/node_modules/yaml/lib/yaml.js:384:46)
at handleInput (/usr/local/lib/node_modules/yaml2json/index.js:31:17)
at Socket. (/usr/local/lib/node_modules/yaml2json/index.js:80:9)
at emitNone (events.js:72:20)
at Socket.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:905:12)
at doNTCallback2 (node.js:450:9)

This simple, valid-YAML document fails:

---
  '{abc}':
    description: abc does not work

It appears the YAML parser doesn't accept non-alphanumeric characters in keys of mappings yet they are valid YAML.

Anyone want to join as a collab and take the responsibility of merging PRs and republishing the site?

Attempt to convert even one of the simplest yaml documents failed instantily because when it encounters the --- document separator it chokes.

---
# that is a valid yaml document and some linters are even requiring us to add the --- separator on the top.
foo: var

Receive an error when using yaml2json to parse the following. Online parsers work fine. Cannot find any similar issues online. I also tried a yaml file that had the strings quoted but got the same issue.

YAML:

---
  foo: bar
  baz:
    - qux
    - quxx
  corge: null
  grault: 1
  garply: true
  waldo: "false"
  fred: undefined

CLI

$ yaml2json ./example.yml

CONSOLE ERROR

/Users/user/.nvm/v0.10.29/lib/node_modules/yaml2json/node_modules/yaml/lib/yaml.js:179
  throw new Error(msg + ', ' + context(this.peek()[1].input))
                                                  ^
TypeError: Cannot read property '1' of undefined
    at Parser.expect (/Users/user/.nvm/v0.10.29/lib/node_modules/yaml2json/node_modules/yaml/lib/yaml.js:179:51)
    at Parser.parseDoc (/Users/user/.nvm/v0.10.29/lib/node_modules/yaml2json/node_modules/yaml/lib/yaml.js:266:8)
    at Parser.parse (/Users/user/.nvm/v0.10.29/lib/node_modules/yaml2json/node_modules/yaml/lib/yaml.js:232:19)
    at Object.exports.eval (/Users/user/.nvm/v0.10.29/lib/node_modules/yaml2json/node_modules/yaml/lib/yaml.js:384:46)
    at handleInput (/Users/ben/.nvm/v0.10.29/lib/node_modules/yaml2json/index.js:31:17)
    at /Users/user/.nvm/v0.10.29/lib/node_modules/yaml2json/index.js:56:9
    at fs.js:271:14
    at Object.oncomplete (fs.js:107:15)

Input

--- 
- 
  instrument: "Lasik 2000"
  pulseDuration: 12
  pulseEnergy: 5.4
  repetition: 1000
  spotSize: 1mm
- 
  instrument: "Lasik 2000"
  pulseDuration: 10
  pulseEnergy: 5.0
  repetition: 500
  spotSize: 2mm

Output:

/usr/local/lib/node_modules/yaml2json/node_modules/yaml/lib/yaml.js:179
  throw new Error(msg + ', ' + context(this.peek()[1].input))
        ^
Error: expected indent after document, near " \n- \n  instrument: \"Lasik"
    at Parser.expect (/usr/local/lib/node_modules/yaml2json/node_modules/yaml/lib/yaml.js:179:9)
    at Parser.parseDoc (/usr/local/lib/node_modules/yaml2json/node_modules/yaml/lib/yaml.js:264:8)
    at Parser.parse (/usr/local/lib/node_modules/yaml2json/node_modules/yaml/lib/yaml.js:232:19)
    at Object.exports.eval (/usr/local/lib/node_modules/yaml2json/node_modules/yaml/lib/yaml.js:384:46)
    at handleInput (/usr/local/lib/node_modules/yaml2json/index.js:31:17)
    at /usr/local/lib/node_modules/yaml2json/index.js:56:9
    at fs.js:268:14
    at Object.oncomplete (fs.js:107:15)

YAMLint.com says it's valid YAML, and conversion works on http://yamltojson.com/

Master has had a merge as recently as three months ago, but the latest release on npmjs.com is two years old. The version number then (and still, in master) is 1.0.2.

I specifically would like this commit because it's required to work around a bug in yaml which results in:

Error: hash not properly dedented

If I use current master directly (instead of npm install yaml2json) this error goes away.

Yaml:

bla:
  yo: [1,2,3,4,5,6]
  foo: bar
  baz: {keep: me, one: lined}

Expected (roughly):

{ "bla":
  { "yo": [1, 2, 3, 4, 5, 6],
    "foo": "bar",
    "baz": {"keep": "me", "one": "lined"}}}

But got:

{
  "bla": {
    "yo": [
      1,
      2,
      3,
      4,
      5,
      6
    ],
    "foo": "bar",
    "baz": {
      "keep": "me",
      "one": "lined"
    }
  }
}

Thoughs?