cooklang-import 0.9.9

A tool for importing recipes into Cooklang format
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70

# Troubleshooting

## Common Errors

### "OPENAI_API_KEY must be set"

Set your API key:

```sh
export OPENAI_API_KEY="your-key-here"
```

Or use a different provider with its corresponding key.

### "No providers available in fallback configuration"

Ensure at least one provider is:
- Enabled in `config.toml` (`enabled = true`)
- Included in `fallback.order`
- Has a valid API key configured

### Rate Limiting

If you encounter rate limits:
1. Enable fallback to use multiple providers
2. Increase `retry_delay_ms` in config
3. Use a different provider temporarily

### Recipe Extraction Failed

If structured extractors fail:
1. The tool falls back to Chrome fetcher for JS-heavy sites
2. Then tries LLM-based text extraction
3. Check if the site requires authentication or has anti-bot protection

### Timeout Errors

Increase the timeout:

```sh
cooklang-import https://example.com/recipe --timeout 90
```

Or in code:

```rust
RecipeImporter::builder()
    .url("...")
    .timeout(Duration::from_secs(90))
    .build()
    .await?;
```

## Debug Logging

Enable debug output:

```sh
RUST_LOG=debug cooklang-import <url>
```

## Migration Notes

### From Environment Variables Only

If upgrading from a version that only used environment variables:

1. **No action required** - Environment variables continue to work
2. **Optional**: Create `config.toml` for advanced features
3. Keep API keys in environment variables for security