-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(cloudflare): add local dev section #1772
Conversation
Added the build step to wrangler.toml example Previously: Any code changes would require a new `nitropack build` followed by restarting `wrangler dev` Now: `wrangler` watches the routes dir and `nitro.config.ts`. On change, `wrangler` dev rebuilds `nitro` Local dev experience when using `wrangler dev` now matches `nitropack dev`
β Live Preview ready!
|
wrangler.toml
to add build-step
Hi and thanks for this PR. Normally , we expect always a build step happens before running platform-specific deployment steps (such as wrangler dev) + we are considering to support cloudflare (and other presets) in dev/watch mode. For this to move forward, i would suggest a new section to the end about adding build steps. |
@pi0 We could change the
This would only trigger when running Leaving the rest of the steps as it was before |
i see but we ideally donβt need to run full build on each dev change. Thatβs why asking to add it as new advanced section until improvements this area. |
100% |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
wrangler.toml
to add build-step
π Linked issue
β Type of change
π Description
Added a build step to wrangler.toml example
Previously:
Any code changes would require a new
nitropack build
followed by restartingwrangler dev
Now:
wrangler
watches the routes dir andnitro.config.ts
. On change,wrangler
dev rebuildsnitro
Local dev experience when usingwrangler dev
now matchesnitropack dev
π Checklist