Remove nodemon and document the unified Vite dev/build server - #4668
Draft
cprecioso wants to merge 2 commits into
Draft
Remove nodemon and document the unified Vite dev/build server#4668cprecioso wants to merge 2 commits into
cprecioso wants to merge 2 commits into
Conversation
Nothing consumed nodemon after the dev server moved into Vite's module runner, so drop `genNodemon`, the `nodemon.json` template and the `nodemon` devDependency. Refresh the comments the previous PRs invalidated (the generated server's tsconfig, package.json and README, and `ExtImport`'s note on which watcher sees what), document the `waspServer()` plugin and the `server` environment in the docs, add a migration step for it, and write one consolidated ChangeLog entry for the whole stack.
Deploying wasp-docs-on-main with
|
| Latest commit: |
c54b689
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6b4327d0.wasp-docs-on-main.pages.dev |
| Branch Preview URL: | https://cprecioso-vite-server-cleanu.wasp-docs-on-main.pages.dev |
15 tasks
cprecioso
had a problem deploying
to
fly-deploy-test
August 11, 2026 13:06 — with 
GitHub Actions
Failure
GitHub Actions
Failure
cprecioso
temporarily deployed
to
railway-deploy-test
August 11, 2026 13:06 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
@wasp.sh/spec
@wasp.sh/wasp-cli
@wasp.sh/wasp-cli-darwin-arm64-unknown
@wasp.sh/wasp-cli-darwin-x64-unknown
@wasp.sh/wasp-cli-linux-arm64-glibc
@wasp.sh/wasp-cli-linux-x64-glibc
@wasp.sh/wasp-cli-linux-x64-musl
commit: |
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
1 participant
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.
Part of the Vite server unification stack (PR 5/5). Base:
cprecioso/vite-unified-dev(#4667).Description
Final PR of the stack: removes the dev machinery the previous PRs made dead, refreshes the comments and docs they invalidated, and writes the user-facing story for the whole stack.
ServerGenerator.genNodemon, theserver/nodemon.jsontemplate and thenodemondevDependency. Nothing consumed them after PR 4 dropped thewatchandbundle-and-startscripts.templates/server/tsconfig.json(the rollup mention and the "we don't run TSC" note, which thebundlescript has contradicted for a while), the leftovercomment-filipkey intemplates/server/package.json, the nodemon paragraph inWasp.AppSpec.ExtImport, and the generated server'sREADME.md(it promisednpm startreloads on changes).web/docs/only):project/custom-vite-config.md:waspServer()in the required configuration, a new "The Server Environment" section (single dev process, production bundling,vite buildstill means "build the client"), and the enforced options the server plugin adds.advanced/accessing-app-config.md: the nodemon prose is replaced by the in-process dev server.guides/deployment/cloud-providers/render.md: a note thatnpm run bundlegoes through the project's root Vite config and the root installwasp buildproduces, so it can't run on its own.vite.configsnippet a user can copy now includeswaspServer()(Tailwind guide, local network testing guide), and thewasp startoutput sample uses the new[ App ]prefix.migration-guide.md: a step for addingwaspServer(), and the "check out the migration guide" line the 0.26.0 ChangeLog section was missing. Note the in-development guide lives atweb/docs/migration-guide.md; theweb/docs/migration-guides/path in the checklist below only exists inversioned_docs.waspc/ChangeLog.md: one consolidated breaking-change entry for the whole stack (plugin requirement, single dev process, in-place server restarts, no dev type-checking, rollup/nodemon gone from devDependencies,bundle/assets/chunks).No
waspc.cabalversion bump: the version was already bumped to0.26.0onmainafter the0.25.0release (commit27c15f522f), and that section of the ChangeLog already carries breaking changes.Left as follow-ups (from the plan): dev seeding through a one-shot module runner, user options for
wasp/server/vite, moving the server typecheck into a Vite plugin, and the openSaaS starter'svite.config.ts, which needswaspServer()when this releases.Type of change
Checklist
I tested my change in a Wasp app to verify that it works as intended.
🧪 Tests and apps:
examples/kitchen-sink/e2e-tests.waspc/data/Cli/templates, as needed.examples/, as needed.examples/tutorials) I updated the tutorial in the docs (and vice versa).📜 Documentation:
web/docs/.🆕 Changelog: (if change is more than just code/docs improvement)
waspc/ChangeLog.mdwith a user-friendly description of the change.web/docs/migration-guides/.versioninwaspc/waspc.cabalto reflect the changes I introduced.