Skip to content

fix: make openapi-effect a drop-in replacement for openapi-fetch#9

Merged
skulidropek merged 4 commits intomainfrom
codex/drop-in-openapi-fetch
Feb 12, 2026
Merged

fix: make openapi-effect a drop-in replacement for openapi-fetch#9
skulidropek merged 4 commits intomainfrom
codex/drop-in-openapi-fetch

Conversation

@skulidropek
Copy link
Contributor

Goal: openapi-effect should be a near 1:1 replacement for openapi-fetch in consumer code, adding an opt-in Effect API.\n\nChanges:\n- Default export + named createClient now re-export openapi-fetch createClient\n- Re-export all openapi-fetch types/exports\n- Effect API remains opt-in via createClientEffect/createClientStrict\n- Build emits dist/index.js for library entry + keeps dist/main.js for template CLI\n\nMotivation: LeadForgeAI should only need to swap imports openapi-fetch -> openapi-effect (minimal diff).

@skulidropek skulidropek force-pushed the codex/drop-in-openapi-fetch branch from 36ea6cb to 587264d Compare February 12, 2026 15:03
@skulidropek skulidropek merged commit 6210b36 into main Feb 12, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant