chore(deps): update all non-major dependencies #2354
Merged
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.
This PR contains the following updates:
2.25.0
->2.26.1
18.7.18
->18.16.16
0.28.22
->0.29.2
18.2.6
->18.2.8
3.11.1
->3.12.0
3.11.1
->3.12.0
2.1.0
->2.2.2
13.4.3
->13.4.4
^0.28.0
->^0.29.0
2.1.9
->2.20.0
Release Notes
changesets/changesets
v2.26.1
Compare Source
Patch Changes
feddc88
Thanks @Andarist! - Callpnpm publish
directly from the directory of the published package. This allowspnpm
to correctly handle configuredpublishConfig.directory
.v2.26.0
Compare Source
Minor Changes
#1033
521205d
Thanks @Andarist! - A new config-levelchangedFilePatterns
option has been added. You can configure it with an array of glob patterns like here:Files that do not match the configured pattern won't contribute to the "changed" status of the package to which they belong. This both affects
changesets add
andchangeset status
.Patch Changes
598136a
,521205d
,521205d
,598136a
,598136a
,521205d
]:v2.25.2
Compare Source
Patch Changes
6cc4300
]:v2.25.1
Compare Source
Patch Changes
#997
4d4d67b
Thanks @JakeGinnivan! - Add error message when running changesets in a repo with workspaces configured but no packages yet#985
8d0115e
Thanks @mino01x! - Fixed an issue with private packages with versions being included in the CLI prompt despite theprivatePackages.version: false
setting.apollographql/apollo-server (apollo-server)
v3.12.0
Compare Source
apollographql/apollo-server (apollo-server-express)
v3.12.0
Compare Source
graphql/dataloader
v2.2.2
Compare Source
Patch Changes
e286f66
Thanks @henrinormak! - Added missing type definition for Dataloader.namev2.2.1
Compare Source
Patch Changes
6d2efb7
Thanks @saihaj! -name
is an optional propertyv2.2.0
Compare Source
Minor Changes
6c758d0
Thanks @SimenB! - Addname
property toDataLoader
. Useful in APM tools.Patch Changes
588a8b6
Thanks @boopathi! - Fix the propagation of sync throws in the batch function to the loader function instead of crashing the process wtih an uncaught exception.fae38f1
Thanks @LinusU! - Fix types for priming cache with promise3cd3a43
Thanks @thekevinbrown! - Resolves an issue where the maxBatchSize parameter wouldn't be fully used on each batch sent to the backend loader.vercel/next.js
v13.4.4
Compare Source
Core Changes
x-forwarded-*
headers to turbopack renders: #50012init.defaultBranch
git con…: #49960swc_core
tov0.76.18
: #50137draftMode
type to GetServerSidePropsContext: #50184node
condition to import resolution: #50007process.env
: #50260_devMiddlewareManifest.json
from router: #50241Documentation Changes
Example Changes
Misc Changes
Credits
Huge thanks to @kwonoj, @wyattjoh, @shuding, @huozhi, @jridgewell, @ijjk, @karlhorky, @lycuid, @MarkAtOmniux, @darshkpatel, @johnta0, @kdy1, @sokra, @timneutkens, @devagrawal09, @ibrahemid, @styfle, @JesseKoldewijn, @padmaia, @Cow258, @javivelasco, and @05lazy for helping!
ramda/ramda
v0.29.0
Compare Source
Added
🆕 addIndexRight
🆕 isNotNil
🆕 swap
🆕 dropRepeatsBy
Removed
Deprecated
Changes
Thank you to everyone who contributed to this release!
cloudflare/workers-sdk
v2.20.0
Compare Source
Minor Changes
e351afcf
Thanks @GregBrimble! - feat: Add support for the undocumented_worker.js/
directory in Pages#3095
133c0423
Thanks @zebp! - feat: add support for placement in wrangler configAllows a
placement
object in the wrangler config with a mode ofoff
orsmart
to configure Smart placement. Enabling Smart Placement can be done in yourwrangler.toml
like:#3140
5fd080c8
Thanks @penalosa! - feat: Support sourcemaps in DevToolsIntercept requests from DevTools in Wrangler to inject sourcemaps and enable folders in the Sources Panel of DevTools. When errors are thrown in your Worker, DevTools should now show your source file in the Sources panel, rather than Wrangler's bundled output.
Patch Changes
#2912
5079f476
Thanks @petebacondarwin! - fix: do not render "value of stdout.lastframe() is undefined" if the output is an empty stringFixes #2907
d0788008
Thanks @dario-piotrowicz! - fix pages building not taking into account the nodejs_compat flag (and improve the related error message)5b234cfd
Thanks @jspspike! - Added output for tail being in "sampling mode"v2.19.0
Compare Source
Minor Changes
c32f514c
Thanks @edevil! - Added initial commands for integrating with Constellation AI.v2.18.0
Compare Source
Minor Changes
#3098
8818f551
Thanks @mrbbot! - fix: improve Workers Sites asset upload reliabilityToo many bulk operations already in progress
error.WRANGLER_LOG=debug
environment variable. A splash of colour has also been added.v2.17.0
Compare Source
Minor Changes
#3004
6d5000a7
Thanks @rozenmd! - feat: teachwrangler docs
to use algolia search indexThis PR lets you search Cloudflare's entire docs via
wrangler docs [search term here]
.By default, if the search fails to find what you're looking for, you'll get an error like this:
If you provide the
--yes
or-y
flag, wrangler will open the docs to https://developers.cloudflare.com/workers/wrangler/commands/, even if the search fails.v2.16.0
Compare Source
Minor Changes
#3058
1bd50f56
Thanks @mrbbot! - chore: upgrademiniflare@3
to3.0.0-next.13
Notably, this adds native support for Windows to
wrangler dev --experimental-local
, logging for incoming requests, and support for a bunch of newer R2 features.Patch Changes
#3058
1bd50f56
Thanks @mrbbot! - fix: disable persistence without--persist
in--experimental-local
This ensures
--experimental-local
doesn't persist data on the file-system, unless the--persist
flag is set.Data is still always persisted between reloads.
#3055
5f48c405
Thanks @rozenmd! - fix: Teach D1 commands to read auth configuration from wrangler.tomlThis PR fixes a bug in how D1 handles a user's accounts. We've updated the D1 commands to read from config (typically via wrangler.toml) before trying to run commands. This means if an
account_id
is defined in config, we'll use that instead of erroring out when there are multiple accounts to pick from.Fixes #3046
#3058
1bd50f56
Thanks @mrbbot! - fix: disable route validation when using--experimental-local
This ensures
wrangler dev --experimental-local
doesn't require a login or an internet connection if aroute
is configured.v2.15.1
Compare Source
Patch Changes
4c55baf9
Thanks @GregBrimble! - feat: Add**/*.wasm?module
as default module rule (alias of**/*.wasm
)86e942bb
Thanks @GregBrimble! - fix: Durable Object proxying websockets over local dev registryv2.15.0
Compare Source
Minor Changes
#2769
0a779904
Thanks @penalosa! - feature: Support modules with--no-bundle
When the
--no-bundle
flag is set, Wrangler now has support for uploading additional modules alongside the entrypoint. This will allow modules to be imported at runtime on Cloudflare's Edge. This respects Wrangler's module rules configuration, which means that only imports of non-JS modules will trigger an upload by default. For instance, the following code will now work with--no-bundle
(assuming theexample.wasm
file exists at the correct path):For JS modules, it's necessary to specify an additional module rule (or rules) in your
wrangler.toml
to configure your modules as ES modules or Common JS modules. For instance, to upload additional JavaScript files as ES modules, add the following module rule to yourwrangler.toml
, which tells Wrangler that all**/*.js
files are ES modules.If you have Common JS modules, you'd configure Wrangler with a CommonJS rule (the following rule tells Wrangler that all
.cjs
files are Common JS modules):In most projects, adding a single rule will be sufficient. However, for advanced usecases where you're mixing ES modules and Common JS modules, you'll need to use multiple rule definitions. For instance, the following set of rules will match all
.mjs
files as ES modules, all.cjs
files as Common JS modules, and thenested/say-hello.js
file as Common JS.If multiple rules overlap, Wrangler will log a warning about the duplicate rules, and will discard additional rules that matches a module. For example, the following rule configuration classifies
dep.js
as both a Common JS module and an ES module:Wrangler will treat
dep.js
as a Common JS module, since that was the first rule that matched, and will log the following warning:This also adds a new configuration option to
wrangler.toml
:base_dir
. Defaulting to the directory of your Worker's main entrypoint, this tells Wrangler where your additional modules are located, and determines the module paths against which your module rule globs are matched.For instance, given the following directory structure:
If your
wrangler.toml
hadmain = "src/js/index.js"
, you would need to setbase_dir = "src"
in order to be able to importsrc/vendor/dependency.js
andsrc/index.html
fromsrc/js/index.js
.Patch Changes
#2957
084b2c58
Thanks @esimons! - fix: Respect querystring params when calling.fetch
on a worker instantiated withunstable_dev
Previously, querystring params would be stripped, causing issues for test cases that depended on them. For example, given the following worker script:
would fail the following test case:
#2840
e311bbbf
Thanks @mrbbot! - fix: makeWRANGLER_LOG
case-insensitive, warn on unexpected values, and fallback tolog
if invalidPreviously, levels set via the
WRANGLER_LOG
environment-variable were case-sensitive.If an unexpected level was set, Wrangler would fallback to
none
, hiding all logs.The fallback has now been switched to
log
, and lenient case-insensitive matching is used when setting the level.eebad0d9
Thanks @kuba-orlik! - fix: allow programmatic dev workers to be stopped and started in a single session3f7a75cc
Thanks @JacobMGEvans! - Fix: Generate Remote URLPrevious URL was pointing to the old cloudflare/templates repo,
updated the URL to point to templates in the workers-sdk monorepo.
v2.14.0
Compare Source
Minor Changes
dc1465ea
Thanks @mrbbot! - chore: upgrademiniflare
to2.13.0
#2914
9af1a640
Thanks @edevil! - feat: add support for send email bindingsSupport send email bindings in order to send emails from a worker. There
are three types of bindings:
does not need to be specified when sending the email but also needs to be a
verified destination address).
addresses.
Patch Changes
#2931
5f6c4c0c
Thanks @Skye-31! - Fix: Pages Dev incorrectly allowing people to turn off local modeLocal mode is not currently supported in Pages Dev, and errors when people attempt to use it. Previously, wrangler hid the "toggle local mode" button when using Pages dev, but this got broken somewhere along the line.
v2.13.0
Compare Source
Minor Changes
#2905
6fd06241
Thanks @edevil! - feat: support external imports fromcloudflare:...
prefixed modulesGoing forward Workers will be providing built-in modules (similar to
node:...
) that can be imported using thecloudflare:...
prefix. This change adds support to the Wrangler bundler to mark these imports as external.163dccf4
Thanks @jspspike@gmail.com! - feature: addwrangler deployment view
andwrangler rollback
subcommandswrangler deployments view [deployment-id]
will get the details of a deployment, including bindings and usage model information.This information can be used to help debug bad deployments.
wrangler rollback [deployment-id]
will rollback to a specific deployment in the runtime. This will be useful in situations like recovering from a baddeployment quickly while resolving issues. If a deployment id is not specified wrangler will rollback to the previous deployment. This rollback only changes the code in the runtime and doesn't affect any code or configurations
in a developer's local setup.
wrangler deployments list
will list the 10 most recent deployments. This command originally existed aswrangler deployments
example of
view <deployment-id>
output:v2.12.3
Compare Source
Patch Changes
e33bea9b
Thanks @WalshyDev! - Changed console.debug for logger.debug in Pages uploading. This will ensure the debug logs are only sent when debug logging is enabled withWRANGLER_LOG=debug
.#2878
6ebb23d5
Thanks @rozenmd! - feat: Add D1 binding support to Email WorkersThis PR makes it possible to query D1 from an Email Worker, assuming a binding has been setup.
As D1 is in alpha and not considered "production-ready", this changeset is a patch, rather than a minor bump to wrangler.
v2.12.2
Compare Source
Patch Changes
5bcc333d
Thanks @GregBrimble! - fix: Prevent compile loop when using_worker.js
andwrangler pages dev
v2.12.1
Compare Source
Patch Changes
#2839
ad4b123b
Thanks @mrbbot! - fix: removevitest
fromwrangler init
's generatedtsconfig.json
types
arrayPreviously,
wrangler init
generated atsconfig.json
with"types": ["@​cloudflare/workers-types", "vitest"]
, even if Vitest tests weren't generated.Unlike Jest, Vitest doesn't provide global APIs by default, so there's no need for ambient types.
8d462c0c
Thanks @GregBrimble! - chore: Remove the--experimental-worker-bundle
option from Pages Functionse3c036d7
Thanks @Cyb3r-Jak3! - feature: include .wrangler directory in gitignore template used withwrangler init
#2806
8d462c0c
Thanks @GregBrimble! - feat: Add--outdir
as an option when runningwrangler pages functions build
.This deprecates
--outfile
when building a Pages Plugin with--plugin
.When building functions normally,
--outdir
may be used to produce a human-inspectable format of the_worker.bundle
that is produced.#2806
8d462c0c
Thanks @GregBrimble! - Enable bundling in Pages Functions by default.We now enable bundling by default for a
functions/
folder and for an_worker.js
in Pages Functions. This allows you to use external modules such as Wasm. You can disable this behavior in Direct Upload projects by using the--no-bundle
argument inwrangler pages publish
andwrangler pages dev
.#2836
42fb97e5
Thanks @GregBrimble! - fix: preserve the entrypoint filename when runningwrangler publish --outdir <dir>
.Previously, this entrypoint filename would sometimes be overwritten with some internal filenames. It should now be based off of the entrypoint you provide for your Worker.
#2828
891ddf19
Thanks @GregBrimble! - fix: Bringpages dev
logging in line withdev
proper'swrangler pages dev
now defaults to logging at thelog
level (rather than the previouswarn
level), and thepages
prefix is removed.#2855
226e63fa
Thanks @GregBrimble! - fix:--experimental-local
withwrangler pages dev
We previously had a bug which logged an error (
local worker: TypeError: generateASSETSBinding2 is not a function
). This has now been fixed.2b641765
Thanks @Skye-31! - Fix: Show correct link for how to create an API token in a non-interactive environmentv2.12.0
Compare Source
Minor Changes
#2810
62784131
Thanks @mrbbot! - chore: upgrade@miniflare/tre
to3.0.0-next.12
, incorporating changes from3.0.0-next.11
Notably, this brings the following improvements to
wrangler dev --experimental-local
:better-sqlite3@​8
, allowing installation on Node 194756d6a1
Thanks @alankemp! - Add new [unsafe.metadata] section to wrangler.toml allowing arbitary data to be added to the metadata section of the uploadPatch Changes
#2539
3725086c
Thanks @GregBrimble! - feat: Add support for thenodejs_compat
Compatibility Flag when bundling a Worker with WranglerThis new Compatibility Flag is incompatible with the legacy
--node-compat
CLI argument andnode_compat
configuration option. If you want to use the new runtime Node.js compatibility features, please remove the--node-compat
argument from your CLI command or your config file.v2.11.1
Compare Source
Patch Changes
ec3e181e
Thanks @penalosa! - fix: Adds aduplex: "half"
property to R2 fetch requests with stream bodies in order to be compatible with undici v5.204ca8c0b0
Thanks @GregBrimble! - fix: Support overriding the next URL in subsequent executions withnext("/new-path")
from within a Pages Pluginv2.11.0
Compare Source
Minor Changes
a9adfbe7
Thanks @penalosa! - Previously, wrangler dev would not work if the root of your zone wasn't behind Cloudflare. This behaviour has changed so that now only the route which your Worker is exposed on has to be behind Cloudflare.#2708
b3346cfb
Thanks @Skye-31! - Feat: Pages now supports Proxying (200 status) redirects in it's _redirects fileThis will look something like the following, where a request to /users/123 will appear as that in the browser, but will internally go to /users/[id].html.
Patch Changes
#2766
7912e63a
Thanks @mrbbot! - fix: correctly detectservice-worker
format when usingtypeof module
Wrangler automatically detects whether your code is a
modules
orservice-worker
format Worker based on the presence of adefault
export
. This check currently works by building your entrypoint withesbuild
and looking at the output metafile.Previously, we were passing
format: "esm"
toesbuild
when performing this check, which enables format conversion. This may introduceexport default
into the built code, even if it wasn't there to start with, resulting in incorrect format detections.This change removes
format: "esm"
which disables format conversion when bundling is disabled. See https://esbuild.github.io/api/#format for more details.#2780
80f1187a
Thanks @GregBrimble! - fix: Ensure we don't mangle internal constructor names in the wrangler bundle when building with esbuildUndici changed how they referenced
FormData
, which meant that when used in our bundle process, we were failing to uploadmultipart/form-data
bodies. This affectedwrangler pages publish
andwrangler publish
.#2720
de0cb57a
Thanks @JacobMGEvans! - Fix: Upgraded to ES2022 for improved compatibilityUpgraded worker code target version from ES2020 to ES2022 for better compatibility and unblocking of a workaround related to issue #2029. The worker runtime now uses the same V8 version as recent Chrome and is 99% ES2016+ compliant. The only thing we don't support on the Workers runtime, the remaining 1%, is the ES2022 RegEx feature as seen in the compat table for the latest Chrome version.
Compatibility table: https://kangax.github.io/compat-table/es2016plus/
resolves #2716
4ede044e
Thanks @mrbbot! - chore: upgrademiniflare
to2.12.1
and@miniflare/tre
to3.0.0-next.10
v2.10.0
Compare Source
Minor Changes
02ea098e
](https://togithub.com/clConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.