`wrangler dev` doesn't restart the server even after re-running the build command...

Has anyone experienced this issue? My wrangler.toml looks like this:

#:schema node_modules/wrangler/config-schema.json
name = "phosphor-server"
main = "build/phosphor-server.min.mjs"
compatibility_date = "2024-07-12"
compatibility_flags = ["nodejs_compat"]
no_bundle = true

[build]
command = "bun run vite build"

#:schema node_modules/wrangler/config-schema.json
name = "phosphor-server"
main = "build/phosphor-server.min.mjs"
compatibility_date = "2024-07-12"
compatibility_flags = ["nodejs_compat"]
no_bundle = true

[build]
command = "bun run vite build"

1 Reply

Cole•4mo ago

I'm on macOS Darwin 23.5.0 arm64 arm with node v21.6.1 Interestingly, if I compile my bundle to a build/_worker.js file and instead run wrangler pages dev ./build, everything works correctly (including the build command). That's pretty jank considering the config will throw if you try to use both a pages_build_output_dir = "./build" with a [build] section... 🫣 While maybe temporary that this works, this is going to work the best for me, because page deployment seems to have more support for interesting tools such as having a unstable_pages.deploy(...) function exported from "wrangler" which is really nice to have in my deployment strategy, since it returns the deployed URL.

Gaming

Programming

`wrangler dev` doesn't restart the server even after re-running the build command...