Can you use a newer go version to build this nice tool? Go 1.19 is known for having critical vulnerabilities. I did some minimal testing using Go 1.22 and it seems to work.

The example given was on unix.. how do we do it in windows please

It seems the issue is only reproducible for certain strings.
The pattern <number><string><underscore><number> is faulty.
There may be more.

See:

$ cat file.yml
---
property: 0testS_1value
###
$ cat file.yml | yaml2json
{"property":"0testS1value"}

@bronze1man My Question is , when I am running it as bash (i.e from terminal ) yaml2json works fine.
But when I run the same with the help of java , it says yaml2json command not found.
Please help me out.

If you run yaml2json on a multi-document YAML file, the output is not valid JSON. It'd be nice to have an option to output an array instead of a JSON stream.

Not a big deal, an easy workaround is to pipe it to jq -s

foo | yaml2json | jq -s -r .

err:

$ yaml2json <(cat foo.yml)
UnknownAlias {_anchorName = "consul_shared"}

foo.yml:

...
consul: *consul_shared
...
consul: &consul_shared
...

Although JSON does not support comments in the usual sense, comments in YAML could be preserved using a suitable key, which could, for example, be "//" by default.

For example, assuming "//" has been specified as the key to use for comments, the following YAML:

# comment on a
a: null

# comment on b
b: 1

# comment on c
c: 2

would become:

{
  "//": {
    "a": "comment on a",
    "b": "comment on b",
    "c": "comment on c"
  },
  "a": null,
  "b": 1,
  "c": 2
}

The binary image supplied with this application is broken on macOS 10.13.2

yaml2json
failed MSpanList_Insert 0x201000 0x35b4e88bf768 0x0
fatal error: MSpanList_Insert

The rebuild of image with following command fixes an issue.

go get -v github.com/bronze1man/yaml2json

I don't know how to run this project.I have done it in my linux system.

When used with input like this:

x:
y:

The 1.3 version binary crashes with a panic, while the 1.2 version handles it correctly (outputting null as the value of the x and y keys.

Looks like the builds/ directory is 4 years old. This is a useful tool, could you support or elaborate on how to build this for all those architectures now. Maybe publish builds as Github releases?

Hi there could you add a flag that outputs the version?

$ yaml2json --version
yaml2json 1.3

There are many use cases for checking the version ...

When?

Converting a large input comprising multiple documents divided with ---. No issues with the same input when using yq for example.

Source of the original file (kubernetes crds):
https://doc.crds.dev/raw/github.com/crossplane/[email protected]

What happened?

$ curl https://doc.crds.dev/raw/github.com/crossplane/[email protected] > in.yaml
$ wc -l in.yaml 
46157 in.yaml
$ yaml2json < in.yaml > out.json
panic: resolveTable item not yet handled: N (with ) [recovered]
	panic: resolveTable item not yet handled: N (with )

goroutine 1 [running]:
github.com/bronze1man/yaml2json/vendor/gopkg.in/yaml%2ev2.handleErr(0xc000113cc8)
	/Users/a/work/yaml2json/src/github.com/bronze1man/yaml2json/vendor/gopkg.in/yaml.v2/yaml.go:249 +0x9a
panic(0x509cc0, 0xc000126eb0)
	/usr/local/go/src/runtime/panic.go:513 +0x1b9
github.com/bronze1man/yaml2json/vendor/gopkg.in/yaml%2ev2.resolve(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/Users/a/work/yaml2json/src/github.com/bronze1man/yaml2json/vendor/gopkg.in/yaml.v2/resolve.go:198 +0xe40
github.com/bronze1man/yaml2json/vendor/gopkg.in/yaml%2ev2.(*decoder).scalar(0xc0003a2040, 0xc00010e070, 0x511a60, 0xc000126ea0, 0x194, 0x511a60)
	/Users/a/work/yaml2json/src/github.com/bronze1man/yaml2json/vendor/gopkg.in/yaml.v2/decode.go:376 +0x92
github.com/bronze1man/yaml2json/vendor/gopkg.in/yaml%2ev2.(*decoder).unmarshal(0xc0003a2040, 0xc00010e070, 0x511a60, 0xc000126ea0, 0x194, 0x1)
	/Users/a/work/yaml2json/src/github.com/bronze1man/yaml2json/vendor/gopkg.in/yaml.v2/decode.go:330 +0xd6
github.com/bronze1man/yaml2json/vendor/gopkg.in/yaml%2ev2.(*decoder).document(0xc0003a2040, 0xc00010e000, 0x511a60, 0xc000126ea0, 0x194, 0xc000113c30)
	/Users/a/work/yaml2json/src/github.com/bronze1man/yaml2json/vendor/gopkg.in/yaml.v2/decode.go:344 +0x7a
github.com/bronze1man/yaml2json/vendor/gopkg.in/yaml%2ev2.(*decoder).unmarshal(0xc0003a2040, 0xc00010e000, 0x511a60, 0xc000126ea0, 0x194, 0x194)
	/Users/a/work/yaml2json/src/github.com/bronze1man/yaml2json/vendor/gopkg.in/yaml.v2/decode.go:320 +0x1d3
github.com/bronze1man/yaml2json/vendor/gopkg.in/yaml%2ev2.(*Decoder).Decode(0xc000113d20, 0x503820, 0xc000126ea0, 0x0, 0x0)
	/Users/a/work/yaml2json/src/github.com/bronze1man/yaml2json/vendor/gopkg.in/yaml.v2/yaml.go:130 +0x1da
github.com/bronze1man/yaml2json/y2jLib.TranslateStream(0x554fa0, 0xc00008c000, 0x7f27482db000, 0xc00008c008, 0xc00008c008, 0x0)
	/Users/a/work/yaml2json/src/github.com/bronze1man/yaml2json/y2jLib/lib.go:16 +0x1fb
main.main()
	src/github.com/bronze1man/yaml2json/main.go:19 +0xa9

Due to the lack of a tool in a comparable simplicity and power for the other way around, i.e json2yaml, I would strongly encourage you to program json2yaml tool in the same way!

I have looked inside this repo to find if it able to convert some YAML specific symbols like .inf, .-inf, .nan, and ~.
In one of my own projects, when I have needed to same conversion from YAML to JSON it was resolved as:

• .inf = 2147483647 (math.MaxInt32)
• -.inf = -2147483648 (math.MinInt32)
• .nan = 0
• ~ = null

And what about YAML multi-document files?
It might be 2 functions where first will fetch only first document (by compatibility reasons) and processes it as JSON, and second fetches all documents and returns array of JSON converted docs.

Could yaml2json be published to Homebrew to make it easier for newbies to install?

I'm getting an error if there's a dictionary and a key named n.

For example:

# ERROR:
$ echo 'n: bar' | yaml2json
type mismatch: expect map key string or int; got: bool

# GOOD:
$ echo 'a: bar' | yaml2json
{"a":"bar"}

Please, make go mod init to support Go 1.11 modules.
It'll allow to use your module simple and in right way.

Go Modules Reference