feat: create dir for output file

[cuhland]

Describe the bug

When the output-file contains a path, then the generation fails.
I want to place the result of the sbom not in the root directory, but in a dedicated build folder for further processing in the pipeline.

To Reproduce

The following call

cyclonedx-npm --output-file build/reports/sbom.json

will cause an ERROR and no sbom is generated.

Error: ENOENT: no such file or directory, open '<path>/build/reports/sbom.json'

Process finished with exit code 254

Expected behavior

The folders are generated if the --output-file argument contains a path.

Environment

• @cyclonedx/cyclonedx-npm version: 1.19.3
• NPM version: 10.9.0
• Node version: v23.1.0
• OS: mac

[jkowalleck]

this is not a bug, but intended behavior.
if the directory of the target file does not exist, the creation of the target file fails.

Expected behavior
The folders are generated if the --output-file argument contains a path.

could you elaborate why this "feature" would be needed?
why don't you create the folder yourself, if it does not exist? don't you have control over your own file system?

[jkowalleck]

the following worked for me:

mkdir -p dist/foo/bar
cyclonedx-npm --output-file dist/foo/bar/bom.cdx.json

[cuhland]

this is not a bug, but intended behavior. if the directory of the target file does not exist, the creation of the target file fails.

I agree that is not a bug, but an enhancement.

could you elaborate why this "feature" would be needed? why don't you create the folder yourself, if it does not exist? don't you have control over your own file system?

For sure, I can create a folder myself. But it is easier for the caller, if the library supports the creation of a directory if needed.

[jkowalleck]

But it is easier for the caller [...]

I understand.

This sounds like a nice-to-have feature, but in fact, I'd consider it a breaking change:
current behavior is to fail if target folder does not exist, yet.
This comment is a remark, not a blocker.