Previously, the implementation of custom builds inside dev assumed it could be a long running process however it's not (else consider that publish would never work).This simplifies the code for both dev and publish. This consolidates some logic into getEntry(), namely including guessWorkerFormat() and custom builds. #567 05b81c5 Thanks - fix: consolidate getEntry() logic For now, this means checking (in order)įor Chrome and Edge, and then failing if neither of those are available. We should force a chromium-based browser to launch. We rely on Chromium-based devtools for debugging workers, so when opening up the devtools URL, #599 7d4ea43 Thanks - Force-open a chromium-based browser for devtools This is because we can't trust the time that a deploy target may provide (like in Expiration changes hanging deploys wrangler-legacy#2224). This switches how we expire static assets with uploads to use expiration_ttl instead of expiration. #649 e0b9366 Thanks - fix: use expiration_ttl to expire assets with #627 ff53f4e Thanks - fix: do not warn about miniflare in the configuration If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. This PR was opened by the Changesets release GitHub action.
0 kommentar(er)
