User limits provided via script metadata on upload
Example configuration:
[limits]
cpu_ms = 20000
#2162a1f212e6 Thanks @WalshyDev! - add support for service bindings in wrangler pages dev by providing the
new --service|-s flag which accepts an array of BINDING_NAME=SCRIPT_NAME
where BINDING_NAME is the name of the binding and SCRIPT_NAME is the name
of the worker (as defined in its wrangler.toml), such workers need to be
running locally with with wrangler dev.
For example if a user has a worker named worker-a, in order to locally bind
to that they'll need to open two different terminals, in each navigate to the
respective worker/pages application and then run respectively wrangler dev and
wrangler pages ./publicDir --service MY_SERVICE=worker-a this will add the
MY_SERVICE binding to pages' worker env object.
Note: additionally after the SCRIPT_NAME the name of an environment can be specified,
prefixed by an @ (as in: MY_SERVICE=SCRIPT_NAME@PRODUCTION), this behavior is however
experimental and not fully properly defined.
#414454800f6f Thanks @a-robinson! - Log a warning when using a Hyperdrive binding in local wrangler dev
wrangler@3.13.1
Patch Changes
#417188f15f61 Thanks @penalosa! - patch: This release fixes some regressions related to running wrangler dev that were caused by internal refactoring of the dev server architecture (#3960). The change has been reverted, and will be added back in a future release.
#3960c36b78b4 Thanks @RamIdeas! - Refactoring the internals of wrangler dev servers (including wrangler dev, wrangler dev --remote and unstable_dev()).
User limits provided via script metadata on upload
Example configuration:
[limits]
cpu_ms = 20000
#2162a1f212e6 Thanks @WalshyDev! - add support for service bindings in wrangler pages dev by providing the
new --service|-s flag which accepts an array of BINDING_NAME=SCRIPT_NAME
where BINDING_NAME is the name of the binding and SCRIPT_NAME is the name
of the worker (as defined in its wrangler.toml), such workers need to be
running locally with with wrangler dev.
For example if a user has a worker named worker-a, in order to locally bind
to that they'll need to open two different terminals, in each navigate to the
respective worker/pages application and then run respectively wrangler dev and
wrangler pages ./publicDir --service MY_SERVICE=worker-a this will add the
MY_SERVICE binding to pages' worker env object.
Note: additionally after the SCRIPT_NAME the name of an environment can be specified,
prefixed by an @ (as in: MY_SERVICE=SCRIPT_NAME@PRODUCTION), this behavior is however
experimental and not fully properly defined.
#414454800f6f Thanks @a-robinson! - Log a warning when using a Hyperdrive binding in local wrangler dev
3.13.1
Patch Changes
#417188f15f61 Thanks @penalosa! - patch: This release fixes some regressions related to running wrangler dev that were caused by internal refactoring of the dev server architecture (#3960). The change has been reverted, and will be added back in a future release.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot]
commented
1 year ago
Bumps wrangler from 3.1.1 to 3.14.0.
Release notes
Sourced from wrangler's releases.
... (truncated)
Changelog
Sourced from wrangler's changelog.
... (truncated)
Commits
fce2666Version Packages (#4208)38fdbe9Support user CPU time limit (#4204)a1f212eService bindings in Pages (#2162)de25f9aUseunstable_devand add e2e tests for service bindings (#4170)485ccf0Standard Pricing messaging (#4196)e81b161Clarify that wrangler d1 execute defaults to remote DB (#4202)116a45eVersion Packages (#4173)8e92717chore: bumpminiflareto3.20231016.0(#4206)6a09b45Update yargs (#4199)54800f6Warn that Hyperdrive bindings do not yet work in local dev (#4144)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show