Re-export more Click exception types

[BenjyWiener]

First Check

• I added a very descriptive title here.
• I used the GitHub search to find a similar question and didn't find it.
• I searched the documentation, with the integrated search.
• I already searched in Google "How to X" and didn't find any information.
• I already read and followed all the tutorials in the docs and didn't find an answer.

Example Code

# N/A

Description

There are currently a number of exceptions that Typer can raise which are no longer exported by typer, including UsageError and most of its subclasses.

In my code I currently catch click.NoSuchOption in order to show a better error message for options that were used in the wrong subcommand (my-cli sub --opt instead of my-cli --opt sub).

I have global error handler that handles common errors, printing tracebacks and extra information only for unknown exceptions using a catch-all except BaseException. I currently catch and re-raise click.Exception so that CLI errors don't get handled by the catch-all.

I also use click.ClickException.error_code and click.UsageError.exit_code to ensure that my specific error codes don't conflict with those used by Typer/Click.

All of these require accessing typer._click on typer 0.26.

I suggest renaming ClickException to TyperException and re-exporting all of the following:

TyperException
UsageError
NoSuchOption
BadOptionUsage
BadArgumentUsage

Operating System

Other

Operating System Details

No response

Project Version

0.26.7

Python Version

3.14

Additional Context

No response

[sueun-dev]

this is probably the closest current maintainer signal: #1816 (comment)

The short version there is that typer._click is intentionally private in 0.26.x, and the suggested path was to open separate threads for the Click capabilities people want exposed as public Typer API. This thread seems like that exact shape.

#1790 is also a useful precedent: Result was handled as a specific re-export question after the vendoring change.