🔗 Linked issue

Resolves #112

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This adds an additional function .catch to a command definition. It works similarly to setup and cleanup, but the error does not bubble all the way up if caught.

This allows for custom error handling that may differ from the default (e.g. changing the console output of a CLI when an uncaught exception occurs anywhere in the app).

Example usage of catch:

const main = defineCommand({
	meta: {
		name: 'my-cli',
		description: 'my cli command'
	},
	/**
	 * @param {import("citty").CommandContext} ctx 
	 * @param {Error} e 
	 */
	catch(ctx, e) {
		console.log("Error occured!", e.message) // -> Error occured! meep
		process.exit(1);
	},

	run() {
		throw new Error("meep")
	}
});

runMain(main);

📝 Checklist

• I have linked an issue or discussion.
• [ ] I have updated the documentation accordingly. There doesn't seem to be a place in the documentation to update, but I did write tests with full coverage