"jsonld compact" adds weird stuff

[ksuszka]

Running following commands:

echo '{"_:a":"b"}' > input.json
echo '{}' > context.json
jsonld compact -c context.json input.json

gives following result:

[
  {
    "@context": "context.json",
    "_:a": "b"
  },
  {
    "@base": {
      "fragment": null,
      "query": null,
      "file": "input.json",
      "directory": "/Users/ksuszka/repos/experiments/tutorial/",
      "path": "/Users/ksuszka/repos/experiments/tutorial/input.json",
      "port": null,
      "hostname": "",
      "password": null,
      "user": null,
      "auth": null,
      "authority": "",
      "scheme": "file",
      "protocol": "file:",
      "href": "file:///Users/ksuszka/repos/experiments/tutorial/input.json",
      "normalizedPath": "/Users/ksuszka/repos/experiments/tutorial/input.json"
    },
    "mappings": {},
    "inverse": {},
    "fastCurieMap": {}
  }
]

I would expect to have this instead:

{
  "_:a": "b"
}

as it is generated on official json-ld playground: http://tinyurl.com/jdrltwu

[iherman]

Just noting that this problem is still open; I have installed the jsonld library and CLI yesterday (2018-07-05) on node.js, and I get the same issue.

(I would expect that the 'weird stuff' are diagnostic messages, as if some debugging flag was set.)

[davidlehn]

I updated jsonld.js dep to 1.0.2 and released 0.3.0. That fixes the nonsense output above but it will still output the context line. I think that's expected based on how it's implemented, but it probably should operate more like the playground. Also need to find time to make updates to handle more of the spec API flags and extra jsonld.js flags (a task noted in #6).

[iherman]

@davidlehn

First of all, thanks.

Will you also release it to npm? At the moment, npm update does not do anything...

[davidlehn]

@iherman Did you get that resolved? I did release 0.3.0. Maybe just try a reinstall if it's not updating.

[iherman]

@davidlehn I have been on vacations for a while. I am back at my desk tomorrow and I will look at this later this week...

[iherman]

@davidlehn it works now indeed. Thanks.

[VladimirAlexiev]

@davidlehn please close