chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nuxt/eslint (source)	^0.7.4 -> ^0.7.5
@nuxt/eslint-config (source)	^0.7.4 -> ^0.7.5
@nuxthub/core (source)	^0.8.10 -> ^0.8.12
eslint (source)	^9.17.0 -> ^9.18.0
pnpm (source)	9.15.1 -> 9.15.4
vue-tsc (source)	^2.1.10 -> ^2.2.0
wrangler (source)	3.99.0 -> 3.103.2

---

Release Notes

nuxt/eslint (@​nuxt/eslint)

v0.7.5

Compare Source

No significant changes

    View changes on GitHub

nuxt-hub/core (@​nuxthub/core)

v0.8.12

Compare Source

compare changes

🚀 Enhancements

• database: Add support for multiple database migrations directories (#​423)

🩹 Fixes

• docs: Migrations fragment identifier (#​417)

📖 Documentation

• Remove using path as async data key (0b15938)
• Remove using path as async data key" (355a8ff)
• Fix async data keys (859a5f8)

❤️ Contributors

• Sébastien Chopin (@​atinux)
• Yali (@​yusufalitangoz)

v0.8.11

Compare Source

compare changes

🚀 Enhancements

• Add Open API tab in Nuxt Devtools with Scalar (91d5016)

🩹 Fixes

• api: Disable cache and prerender on /api/_hub/** (#​414)

📖 Documentation

• Add blog post about libsodium (#​400)
• NuxtHub github action & app (#​390)
• List supported package managers (#​407)
• Add note for sync issue with private github repo (46fc4e3)
• deploy: Correct path for linking repository to project and migration ti GH Actions (#​411)

🏡 Chore

• Update deps (#​415)

❤️ Contributors

• Sébastien Chopin (@​atinux)
• GiveGet giveget.ee@gmail.com
• Rihan (@​RihanArfan)

eslint/eslint (eslint)

v9.18.0

Compare Source

pnpm/pnpm (pnpm)

v9.15.4

Compare Source

v9.15.3

Compare Source

v9.15.2: pnpm 9.15.2

Compare Source

Patch Changes

• Fixed publish/pack error with workspace dependencies with relative paths #​8904. It was broken in v9.4.0 (398472c).
• Use double quotes in the command suggestion by pnpm patch on Windows #​7546.
• Do not fall back to SSH, when resolving a git-hosted package if git ls-remote works via HTTPS #​8906.
• Improve how packages with blocked lifecycle scripts are reported during installation. Always print the list of ignored scripts at the end of the output. Include a hint about how to allow the execution of those packages.

Platinum Sponsors

Gold Sponsors

vuejs/language-tools (vue-tsc)

v2.2.0

Compare Source

cloudflare/workers-sdk (wrangler)

v3.103.2

Compare Source

Patch Changes

• #​7804 16a9460 Thanks @​vicb! - fix(wrangler): use require.resolve to resolve unenv path

v3.103.1

Compare Source

Patch Changes

• #​7798 a1ff045 Thanks @​CarmenPopoviciu! - Reverts #​7720 as it introduced breakage in some of the C3 templates (eg. Nuxt)

v3.103.0

Compare Source

Minor Changes

• #​5086 8faf2c0 Thanks @​dario-piotrowicz! - add --strict-vars option to wrangler types

  add a new --strict-vars option to wrangler types that developers can (by setting the
  flag to false) use to disable the default strict/literal types generation for their variables

  opting out of strict variables can be useful when developers change often their vars values,
  even more so when multiple environments are involved

v3.102.0

Compare Source

Minor Changes

• #​7592 f613276 Thanks @​garrettgu10! - New filter validation logic supporting set and range queries in Vectorize CLI

Patch Changes

• #​7750 df0e5be Thanks @​andyjessop! - bug: Removes the (local) tag on Vectorize bindings in the console output of wrangler dev, and adds-in the same tag for Durable Objects (which are emulated locally in wrangler dev).

• #​7732 d102b60 Thanks @​Ankcorn! - fix pages secret bulk copy

• #​7706 c63f1b0 Thanks @​penalosa! - Remove the server-based dev registry in favour of the more stable file-based dev registry. There should be no user-facing impact.

• Updated dependencies [8e9aa40]:

  • miniflare@3.20241230.2

v3.101.0

Compare Source

Minor Changes

• #​7534 7c8ae1c Thanks @​cmackenzie1! - feat: Use OAuth flow to generate R2 tokens for Pipelines

• #​7674 45d1d1e Thanks @​Ankcorn! - Add support for env files to wrangler secret bulk i.e. .dev.vars

  Run wrangler secret bulk .dev.vars to add the env file

  //.dev.vars
  KEY=VALUE
  KEY_2=VALUE

  This will upload the secrets KEY and KEY_2 to your worker

• #​7442 e4716cc Thanks @​petebacondarwin! - feat: add support for redirecting Wrangler to a generated config when running deploy-related commands

  This new feature is designed for build tools and frameworks to provide a deploy-specific configuration,
  which Wrangler can use instead of user configuration when running deploy-related commands.
  It is not expected that developers of Workers will need to use this feature directly.

Affected commands

The commands that use this feature are:

• wrangler deploy
• wrangler dev
• wrangler versions upload
• wrangler versions deploy
• wrangler pages deploy
• wrangler pages build
• wrangler pages build-env

Config redirect file

When running these commands, Wrangler will look up the directory tree from the current working directory for a file at the path .wrangler/deploy/config.json. This file must contain only a single JSON object of the form:

{ "configPath": "../../path/to/wrangler.json" }

When this file exists Wrangler will follow the configPath (relative to the .wrangler/deploy/config.json file) to find an alternative Wrangler configuration file to load and use as part of this command.

When this happens Wrangler will display a warning to the user to indicate that the configuration has been redirected to a different file than the user's configuration file.

Custom build tool example

A common approach that a build tool might choose to implement.

• The user writes code that uses Cloudflare Workers resources, configured via a user wrangler.toml file.

  name = "my-worker"
  main = "src/index.ts"
  [[kv_namespaces]]
  binding = "<BINDING_NAME1>"
  id = "<NAMESPACE_ID1>"

  Note that this configuration points main at user code entry-point.

• The user runs a custom build, which might read the wrangler.toml to find the entry-point:

  > my-tool build

• This tool generates a dist directory that contains both compiled code and a new deployment configuration file, but also a .wrangler/deploy/config.json file that redirects Wrangler to this new deployment configuration file:

  - dist
    - index.js
  	- wrangler.json
  - .wrangler
    - deploy
  	  - config.json
  

  The dist/wrangler.json will contain:

  {
    "name": "my-worker",
    "main": "./index.js",
    "kv_namespaces": [
      { "binding": "<BINDING_NAME1>", "id": "<NAMESPACE_ID1>" }
    ]
  }

  And the .wrangler/deploy/config.json will contain:

  {
    "configPath": "../../dist/wrangler.json"
  }

• #​7685 9d2740a Thanks @​vicb! - allow overriding the unenv preset.

  By default wrangler uses the bundled unenv preset.

  Setting WRANGLER_UNENV_RESOLVE_PATHS allow to use another version of the preset.
  Those paths are used when resolving the unenv module identifiers to absolute paths.
  This can be used to test a development version.

• #​7694 f3c2f69 Thanks @​joshthoward! - Default wrangler d1 export to --local rather than failing

Patch Changes

• #​7456 ff4e77e Thanks @​andyjessop! - chore: removes --experimental-versions flag, as versions is now GA.

• #​7712 6439347 Thanks @​penalosa! - Remove CF-Connecting-IP for requests to the edge preview

• #​7703 e771fe9 Thanks @​petebacondarwin! - include the top level Worker name in the parsed config structure

• #​7576 773bda8 Thanks @​cmackenzie1! - Remove defaults for batch-max-* pipeline parameters and define value ranges

• Updated dependencies [2c76887, 78bdec5]:

  • miniflare@3.20241230.1

v3.100.0

Compare Source

Minor Changes

• #​7604 6c2f173 Thanks @​CarmenPopoviciu! - feat: Capture Workers with static assets in the telemetry data

  We want to measure accurately what this number of Workers + Assets projects running in remote mode is, as this number will be a very helpful data point down the road, when more decisions around remote mode will have to be taken.

  These changes add this kind of insight to our telemetry data, by capturing whether the command running is in the context of a Workers + Assets project.

  N.B. With these changes in place we will be capturing the Workers + Assets context for all commands, not just wrangler dev --remote.

Patch Changes

• #​7581 cac7fa6 Thanks @​vicb! - chore(wrangler): update unenv dependency version

  unenv now uses the workerd implementation on node:dns
  See the unjs/unenv#376

• #​7625 d8fb032 Thanks @​vicb! - feat(wrangler): use unenv builtin dependency resolution

  Moving away from require.resolve() to handle unenv aliased packages.
  Using the unenv builtin resolution will allow us to drop the .cjs file from the preset
  and to override the base path so that we can test the dev version of the preset.

• #​7533 755a27c Thanks @​danielgek! - Add warning about the browser rendering not available on local

• #​7614 8abb43f Thanks @​vicb! - chore(wrangler): update unenv dependency version

  The updated unenv contains a fix for the module resolution,
  see unjs/unenv#378.
  That bug prevented us from using unenv module resolution,
  see #​7583.

• Updated dependencies [b4e0af1]:

  • miniflare@3.20241230.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[cloudflare-workers-and-pages]

Deploying hub-starter-p2s5 with    Cloudflare Pages

Latest commit:	87463ca
Status:	✅  Deploy successful!
Preview URL:	https://f9067317.hub-starter-p2s5.pages.dev
Branch Preview URL:	https://renovate-all-minor-patch.hub-starter-p2s5.pages.dev

View logs