How to share Hono RPC client type with frontend package?
We have a Hono backend application using Prisma ORM.
One day our frontend application added the backend package as a dependency to use Hono RPC.
However, this led to the following error since PrismaClient only works in a Node.js runtime:
This happens because the frontend app has a direct dependency on the backend app.
Is there a best practice for sharing only the Hono RPC client types with another package?
5 Replies
assuming the frontend has tree shaking, (if it is using vite, it is on by default)
then it can add the backend as a devDependency, and it should only use
type imports
preferably, the backend should export the type
alternatively, if you are fine having a build artifact, you can compile .d.ts files and give them to the frontendTSConfig Reference - Docs on every TSConfig option
From allowJs to useDefineForClassFields the TSConfig reference includes information about all of the active compiler flags setting up a TypeScript project.
made a monorepo example
https://github.com/ArjixWasTaken/hono-monorepo-example
GitHub
GitHub - ArjixWasTaken/hono-monorepo-example
Contribute to ArjixWasTaken/hono-monorepo-example development by creating an account on GitHub.
since I couldn't find a satisfactory one online
will keep expanding on it
My bad, it is because I mistakenly have my frontend package import directly from the db package using Prisma.
Thank you!