Summary
README.md line 87 documents receivedRedirectUri as string | null | undefined, but src/types/index.ts:156 declares the type as string | undefined (no null). A consumer following the README and passing null will get a TypeScript error.
What I observed
README.md:87:
| receivedRedirectUri | string \| null \| undefined | ...
src/types/index.ts:156:
receivedRedirectUri?: string;
The type only permits string | undefined.
Impact
Consumers reading the README and explicitly passing null (e.g., for an "OAuth not yet completed" branch) hit a TypeScript compile error. Either the type needs to widen to accept null, or the README needs to drop | null.
Suggested fix
Pick one of:
- Widen the type to match README:
- receivedRedirectUri?: string;
+ receivedRedirectUri?: string | null;
- Or update README to match the type by removing
| null.
Option 2 is the minimal, low-risk path unless the Plaid Link SDK actually accepts null semantically at runtime.
Summary
README.mdline 87 documentsreceivedRedirectUriasstring | null | undefined, butsrc/types/index.ts:156declares the type asstring | undefined(nonull). A consumer following the README and passingnullwill get a TypeScript error.What I observed
README.md:87:src/types/index.ts:156:The type only permits
string | undefined.Impact
Consumers reading the README and explicitly passing
null(e.g., for an "OAuth not yet completed" branch) hit a TypeScript compile error. Either the type needs to widen to acceptnull, or the README needs to drop| null.Suggested fix
Pick one of:
| null.Option 2 is the minimal, low-risk path unless the Plaid Link SDK actually accepts
nullsemantically at runtime.