## TL;DR
The pre-built provider package for your provider/version/language does not exist. Either pick a supported version or generate the bindings locally: after init, run `cdktf provider add "aws@~>5.0"` (your provider and version).

## The error
```
aws: Error: Pre-built provider information not found
```
Seen when running e.g. `cdktf init --template="typescript" --providers="aws"`.

## Fix it
1. Init without providers: `cdktf init --template="typescript"` (skip `--providers`).
2. Add the provider with local generation: `cdktf provider add "aws@~>5.0"` (adjust name/version).
3. If you need a specific version, check that pre-built bindings exist for it; otherwise local generation is the way.
4. Run `cdktf synth` to confirm the bindings work.

Expected result: provider bindings generate and synth succeeds.

## When to use this
- `cdktf init --providers="..."` fails with "Pre-built provider information not found"
- You requested a provider version with no pre-built package for your language

## When NOT to use this
- Init succeeds but `cdktf get` fails (different stage)
- The provider name is misspelled (fix the name first)

## Root cause
Pre-built provider packages are published per provider, version, and language. Not every combination exists (new provider versions, less common languages). When the lookup misses, init aborts instead of falling back to local generation; running `cdktf provider add` afterward performs the local schema-driven generation that always works.

## Edge cases
- `latest` can resolve to a version with no pre-built package yet; pin a version with local generation instead.