Hey HN - in addition to the linked codebase, we wrote a blog about the general challenges involved with "refactoring" a backend-facing REST API to also provide a frontend-facing React API (of hooks and components):
https://clerk.dev/blog/refactoring-stripes-api-for-frontend-...
What is the use case for your billing being directly tied to your front-end, and not the back-end? I'd think that opens up a much larger surface area for security problems?
Hey HN - in addition to the linked codebase, we wrote a blog about the general challenges involved with "refactoring" a backend-facing REST API to also provide a frontend-facing React API (of hooks and components): https://clerk.dev/blog/refactoring-stripes-api-for-frontend-...