chore(deps): update all non-major dependencies #42
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:
^1.2.4
->^1.2.5
^1.2.57
->^1.2.59
^1.2.43
->^1.2.45
^1.5.2
->^1.7.1
^3.2.0
->^3.3.0
^0.17.1
->^0.17.2
^22.16.4
->^22.17.0
^0.44.3
->^0.44.4
^9.31.0
->^9.32.0
^3.0.1
->^3.0.4
^4.24.4
->^4.26.1
Release Notes
nuxt/eslint (@nuxt/eslint)
v1.7.1
Compare Source
🐞 Bug Fixes
eslint-typegen.d.ts
innuxt.node.d.ts
, close #596 - by @antfu in https://github.com/nuxt/eslint/issues/596 (ab74e)View changes on GitHub
v1.7.0
Compare Source
🚀 Features
View changes on GitHub
v1.6.0
Compare Source
🐞 Bug Fixes
eslint-plugin-import-x
as default, close #590 - by @antfu in https://github.com/nuxt/eslint/issues/590 (e43d6)View changes on GitHub
nuxt/ui-pro (@nuxt/ui-pro)
v3.3.0
Compare Source
drizzle-team/drizzle-orm (drizzle-orm)
v0.44.4
Compare Source
eslint/eslint (eslint)
v9.32.0
Compare Source
vuejs/language-tools (vue-tsc)
v3.0.4
Compare Source
Features
Bug Fixes
skipTemplateCodegen
when exposing$slots
- Thanks to @KazariEX!Other Changes
checkUnknownEvents
andcheckUnknownComponents
in sfc (#5537) - Thanks to @KazariEX!v3.0.3
Compare Source
Bug Fixes
node_modules
based on file's directory (#5525) - Thanks to @KazariEX!Other Changes
v3.0.2
Compare Source
Features
globalTypesPath
option for non-npm like environment (#5505) - Thanks to @KazariEX!Bug Fixes
/
or)
- Thanks to @KazariEX!colorizedBracketPairs
config for plaintext<component>
withoutis
prop as normal component - Thanks to @KazariEX!@vue/typescript-plugin
last (#5483)name
value of<slot>
- Thanks to @KazariEX!allowJs
to reactivity analyze host - Thanks to @KazariEX!md
for markdown (#5497) - Thanks to @KazariEX!module
from template completion - Thanks to @KazariEX!Other Changes
minimatch
topicomatch
(#5499) - Thanks to @KazariEX!.d.${ext}.ts
file exists (volarjs/volar.js#277)cloudflare/workers-sdk (wrangler)
v4.26.1
Compare Source
Patch Changes
#10061
f8a80a8
Thanks @emily-shen! - feat(containers): try to automatically get the socket path that the container engine is listening on.Currently, if your container engine isn't set up to listen on
unix:///var/run/docker.sock
(or isn't symlinked to that), then you have to manually set this via thedev.containerEngine
field in your Wrangler config, or via the env varsWRANGLER_DOCKER_HOST
. This change means that we will try and get the socket of the current context automatically. This should reduce the occurrence of opaqueinternal error
s thrown by the runtime when the daemon is not listening onunix:///var/run/docker.sock
.In addition to
WRANGLER_DOCKER_HOST
,DOCKER_HOST
can now also be used to set the container engine socket address.#10048
dbdbb8c
Thanks @vicb! - pass the compatibility date and flags to the unenv preset#10096
687655f
Thanks @vicb! - bump unenv to 2.0.0-rc.19#9897
755a249
Thanks @edmundhung! - fix: wrangler types should infer the types of the default worker entrypointUpdated dependencies [
82a5b2e
,f8f7352
,2df1d06
,dbdbb8c
,5991a9c
,687655f
]:v4.26.0
Compare Source
Minor Changes
#10016
c5b291d
Thanks @emily-shen! - Interactively handlewrangler deploy
s that are probably assets-only, where there is no config file and flags are incorrect or missing.For example:
npx wrangler deploy ./public
will now ask if you meant to deploy a folder of assets only, ask for a name, set the compat date and then ask whether to write your choices out towrangler.json
for subsequent deployments.npx wrangler deploy --assets=./public
will now ask for a name, set the compat date and then ask whether to write your choices out towrangler.json
for subsequent deployments.In non-interactive contexts, Wrangler will error as it currently does.
#9971
19794bf
Thanks @edmundhung! - Improved script source display on the pretty error screenPatch Changes
#9800
3d4f946
Thanks @helloimalastair! - remove banner from r2 getobject in pipe mode#9910
7245101
Thanks @dario-piotrowicz! - make sure that the ready-on message is printed after the appropriate runtime controller is readyfix the fact that when starting a local (or remote) dev session the log saying
Ready on http://localhost:xxxx
could be displayed before the runtime is actually ready to handle requests (this is quite noticeable when locally running dev sessions with containers, where the ready message currently gets displayed before the container images building/pulling process)#10031
823cba8
Thanks @vicb! - wrangler and vite-plugin now depend upon the latest version of unenv-preset#10032
154acf7
Thanks @dario-piotrowicz! - add support for containers in wrangler multiworker devcurrently when running
wrangler dev
with different workers (meaning that the-c|--config
flag is used multiple times) containers are not being included, meaning that trying to interact with them at runtime would not work and cause errors instead. The changes here address the above making wrangler correctly detect and wire up the containers.#9988
7fb0bfd
Thanks @penalosa! - Correctly labelmtls
remote bindings warningUpdated dependencies [
823cba8
,19794bf
,059a39e
]:v4.25.1
Compare Source
Patch Changes
#10000
c02b067
Thanks @emily-shen! - Include more (sanitised) user errors in telemetry.We manually vet and sanitised error messages before including them in our telemetry collection - this PR just includes a couple more.
#9996
b0217f9
Thanks @nikitassharma! - Disallow users from pushing images with unsupported platforms to the container image registry#10009
e87198a
Thanks @gpanders! - Fix containers diff output when using JSONC config files#9976
ad02ad3
Thanks @dario-piotrowicz! - add warning for when users runwrangler dev --remote
with (enabled) containers#9819
0c4008c
Thanks @CarmenPopoviciu! - feat(vite-plugin): Add containers support invite dev
Adds support for Cloudflare Containers in
vite dev
. Please note that at the time of this PR a container image can only specify the path to aDockerfile
. Support for registry links will be added in a later version, as will containers support invite preview
.Updated dependencies [
189fe23
,7e5585d
]:v4.25.0
Compare Source
Minor Changes
9f0c175
Thanks @thomasgauvin! - Added rename namespace command to Workers KVPatch Changes
6cc24c0
Thanks @emily-shen! - Add more thorough validation to containers configurationConfiguration
📅 Schedule: Branch creation - "on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 was generated by Mend Renovate. View the repository job log.