fix(cli): add try/catch block to create config file

[maiieul]

What is it?

• Feature / enhancement
• Bug
• Docs / tests
• Other

Why is it needed?

Checklist:

• My code follows the developer guidelines of this project
• I have performed a self-review of my own code
• I have ran pnpm change and documented my changes
• I have add necessary docs (if needed)
• Added new tests to cover the fix / functionality

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0ad902d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Last Commit Build: 0ad902d

@qwik-ui/headless(0ad902d):

npm i https://pkg.pr.new/qwikifiers/qwik-ui/@qwik-ui/headless@0ad902d    

Pull Request Build: #763

@qwik-ui/headless(#763):

npm i https://pkg.pr.new/qwikifiers/qwik-ui/@qwik-ui/headless@763    

[TheMcnafaha]

It's unix tradition that cli programs that error out send a positive integer value to stdout or stderr. If this script is very close to the user, it probably makes sense to send the error message to stdout. If the script is further away, or it runs in the background, stderr is usually the go to.

It appears that this is convention is already being used through this function:

function exitWithError(message: string) {
  log.error(message);
  cancel();
  process.exit(1);
}

Do you think it would make sense to throw an error that writes to stdout if the config file is not written? And if not, what exactly is the point of a try catch that only sends a console log? If the error is worth catching I would think it's worth throwing too.