[BUG] JSONL exporter adds trailing comma

[bf-rbrown]

Is there an existing issue for this?

• I have searched the existing issues.

Current Behavior

JSONL format is to be newline delimited: https://jsonlines.org/.
PR #5705 introduced a comma into the -jsonl-output parameter:
line 90

This makes the output file not jsonline compliant and throws errors when parsing:

$ cat output.testing | jq 1>/dev/null
parse error: Expected value before ',' at line 1, column 33773

Expected Behavior

-jsonl-export flag should produce a jsonl file that is newline delimited without a trailing comma.

Steps To Reproduce

Run a nuclei scan with the -jsonl-export flag
observe the trailing comma in the results.jsonl file.

Relevant log output

Environment

- OS: Ubuntu
- Nuclei: v3.3.6
- Go: go1.22.0

Anything else?

No response

[ehsandeep]

@kchason was it intentional change here https://github.com/projectdiscovery/nuclei/pull/5705/files#diff-3318b3220dac210ed7ff197dab8d5dca1820c39754f9b4ba37ad6a1a209fcd56R90? looks like it broke jsonl fomatting with -jle option.

[kchason]

@kchason was it intentional change here https://github.com/projectdiscovery/nuclei/pull/5705/files#diff-3318b3220dac210ed7ff197dab8d5dca1820c39754f9b4ba37ad6a1a209fcd56R90? looks like it broke jsonl fomatting with -jle option.

No, definitely not intentional to break the format. I'll take a look

[kchason]

@kchason was it intentional change here https://github.com/projectdiscovery/nuclei/pull/5705/files#diff-3318b3220dac210ed7ff197dab8d5dca1820c39754f9b4ba37ad6a1a209fcd56R90? looks like it broke jsonl fomatting with -jle option.

No, definitely not intentional to break the format. I'll take a look

Sorry about that! I've got a patch in to remove the trailing commas at: #5864

[ehsandeep]

@kchason np, it's being fixed in #5861, can you confirm the same?