/Knowledge/sources/honojs__hono/llms-full/rpc-known-issues-ide-performance-compile-your-code-before-using-it-recommended--part-02--e9e9fdd2005b.md
RPC: Known issues > IDE performance > Compile your code before using....
RPC: Known issues IDE performance Compile your code before using it (recommended) (part 02) Source evidence: /Sources/honojs hono/provenance.md Canonical cit...
RPC: Known issues > IDE performance > Compile your code before using it (recommended) (part 02)
Source evidence: /Sources/honojs__hono/provenance.md Canonical citation: https://hono.dev/llms-full.txt#compile-your-code-before-using-it-recommended
Summary
If your project is a monorepo, this solution does fit well. Using a tool like turborepo, you can easily separate the server project and the client project and get better integration managing dependencie...
Content
If your project is a monorepo, this solution does fit well. Using a tool like turborepo, you can easily separate the server project and the client project and get better integration managing dependencies between them. Here is a working example.
You can also coordinate your build process manually with tools like concurrently or npm-run-all.
Metadata
{
"chunk_index": 1,
"citation": "https://hono.dev/llms-full.txt#compile-your-code-before-using-it-recommended",
"coverage_role": "overview",
"qualified_title": "Hono / llms-full / RPC > Known issues > IDE performance > Compile your code before using it (recommended) (2)",
"retrieved_at": "2026-07-02T05:51:01Z",
"section_index": 72,
"source_id": "/honojs/hono",
"source_type": "llms_full",
"target_label": "llms-full",
"title": "RPC: Known issues > IDE performance > Compile your code before using it (recommended) (part 02)",
"upstream_url": "https://hono.dev/llms-full.txt",
"version": "2026"
}