docs: add full-stack monorepo tutorial (Node frontend + Deno backend)#3307
Open
bartlomieju wants to merge 1 commit into
Open
docs: add full-stack monorepo tutorial (Node frontend + Deno backend)#3307bartlomieju wants to merge 1 commit into
bartlomieju wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a tutorial under
examples/tutorialsthat walks through a monorepo with aVite + React frontend running on Node, a Deno HTTP backend, and a shared package
of TypeScript code that both sides import by name through a single Deno
workspace.
The existing workspaces docs cover the building blocks (mixing
deno.jsonandpackage.jsonmembers, npm/pnpm compatibility, catalogs), but never assemblethem into the cross-runtime frontend/backend setup that people keep asking for.
This fills that gap with an end-to-end worked example: root workspace config,
a shared package, the Deno backend, the Vite frontend (using
@deno/vite-pluginso Vite resolves the workspace member), anddeno checktype-checking all three members together.
I built and ran the project while writing this: the backend serves the API using
the shared code, the Vite dev server proxies
/apito it,vite buildbundlesthe shared package, and
deno checkpasses across the whole workspace.Closes #1714.