1# Hybrid Convex Components
2 
3Read this file only when the user explicitly wants a hybrid setup.
4 
5## What This Means
6 
7A hybrid component combines a local Convex component with shared library code.
8 
9This can help when:
10 
11- the user wants a local install but also shared package logic
12- the component needs extension points or override hooks
13- some logic should live in normal TypeScript code outside the component
14  boundary
15 
16## Default Advice
17 
18Treat hybrid as an advanced option, not the default.
19 
20Before choosing it, ask:
21 
22- Why is a plain local component not enough?
23- Why is a packaged component not enough?
24- What exactly needs to stay overridable or shared?
25 
26If the answer is vague, fall back to local or packaged.
27 
28## Risks
29 
30- More moving parts
31- Harder upgrades and backwards compatibility
32- Easier to blur the component boundary
33 
34## Checklist
35 
36- [ ] User explicitly needs hybrid behavior
37- [ ] Local-only and packaged-only options were considered first
38- [ ] The extension points are clearly defined before coding
39