string with ~ break Dry.parse

Use case that break parse:

console.log(Dry.parse('{"path": "~/projects"}'));

return {"path": undefined}

for internal ref usage, it should not be string that can easily by used by user. Maybe something like:

{"__dry__": "ref", "value": "projects"}

if the object have prop __dry__ it mean it internal object and not real object provided by user.

[nevcos]

+1 for using an object for references.

[skerit]

An earlier iteration of json-dry actually contained its own json.js based parser, but it was more trouble than it’s worth.

Also: the stringifying is an afterthought. Dry.stringify is actually just a JSON.stringify wrapper around Dry.toDryObject.

So json-dry actually first creates an intermediate object and then stringifies that using the built-in JSON parser. And yeah: this is much faster than using a custom stringifier/parser 😃

If you’re wondering why such an intermediate object would be useful: it’s for times when you can use a structured clone (like in IndexedDB or web workers), which is (again) a lot faster.

And backwards compatibility with json is important. If you would first use JSON.parse ton a json-dry string you would get a valid object. That valid object can then still be given to Dry.parse