CLI: Json Complex Object outputting all keys as headers

I have a complex JSON object in a file that when running via the CLI outputs the keys as headers

jsonexport complex.json output.csv

complex.json

{
  "complex": {
    "object": 1,
    "that": 2
  },
  "has": 3,
  "nested": {
    "keys": true
  }
}

output.csv

complex.object,complex.that,has,nested.keys
1,2,3,true

but running it via the online demo page https://kaue.github.io/jsonexport/demo/?json={"complex":{"object":1,"that":2},"has":3,"nested":{"keys":true}}&options={}

it comes out as expected

complex.object,1
complex.that,2
has,3
nested.keys,true

[AckerApple]

Acknowledged but not expecting immediate reaction without tighter connection to what is the cause.

I have an educated guess: The options in the demo, even when blank/default I believe, are still sending those blank/default values which perhaps are being seeing as altering arguments…

If you catch my drift above, our goal would be to console log the options in the demo and then exactly send those options in your NodeJs usage.

Based on your skill level, if you cloned our gh-pages branch and console logged the options at runtime you could get our answer. The file to edit would be gh-pages/demo/src/index.js@update:45

Good luck and may Feb 4th be with you

[kaue]

Yeah, we should be good here @AckerApple 😃 forgot to check the issues, still have a lot to catch up