Update all non-major dependencies - #35

v7.1.2

Compare Source

Patch Changes

• fix: resolve the absolute path of the Wrangler config setting assets.directory in case the config file is in a different directory than the root project (#​14036)

• Updated dependencies [793ae28]:

  • @​sveltejs/kit@​2.27.0

v2.27.0

Compare Source

Minor Changes

• feat: remote functions (#​13986)

v2.9.0

Compare Source

Minor Changes

• feat(CheckboxGroup): add readonly prop/functionality (#​1688)

• feat(Checkbox): add readonly prop/functionality (#​1688)

Patch Changes

• fix(Calendar): resolve race condition in month navigation (#​1686)

v2.8.14

Compare Source

Patch Changes

• fix(Menubar): ensure extension exists in import (#​1684)

• fix(Popover): ensure when using a customAnchor, outside interactions are properly handled (#​1679)

• fix(TimeField): ensure input value is string (#​1681)

• fix(Select): ensure required enforced when type='multiple' (#​1685)

v1.54.2

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/36714 - [Regression]: Codegen is not able to launch in Administrator Terminal on Windows (ProtocolError: Protocol error)https://github.com/microsoft/playwright/issues/368288 - [Regression]: Playwright Codegen keeps spamming with selected optiohttps://github.com/microsoft/playwright/issues/3681010 - [Regression]: Starting Codegen with target language doesn't work anymore

Browser Versions

• Chromium 139.0.7258.5
• Mozilla Firefox 140.0.2
• WebKit 26.0

This version was also tested against the following stable channels:

• Google Chrome 140
• Microsoft Edge 140

v10.14.0

Compare Source

Minor Changes

• Added support for JavaScript runtime resolution

  Declare Node.js, Deno, or Bun in devEngines.runtime (inside package.json) and let pnpm download and pin it automatically.

  Usage example:

  {
    "devEngines": {
      "runtime": {
        "name": "node",
        "version": "^24.4.0",
        "onFail": "download" (we only support the "download" value for now)
      }
    }
  }

  How it works:

  1. pnpm install resolves your specified range to the latest matching runtime version.
  2. The exact version (and checksum) is saved in the lockfile.
  3. Scripts use the local runtime, ensuring consistency across environments.

  Why this is better:

  1. This new setting supports also Deno and Bun (vs. our Node-only settings useNodeVersion and executionEnv.nodeVersion)
  2. Supports version ranges (not just a fixed version).
  3. The resolved version is stored in the pnpm lockfile, along with an integrity checksum for future validation of the Node.js content's validity.
  4. It can be used on any workspace project (like executionEnv.nodeVersion). So, different projects in a workspace can use different runtimes.
  5. For now devEngines.runtime setting will install the runtime locally, which we will improve in future versions of pnpm by using a shared location on the computer.

  Related PR: #​9755.

• Add --cpu, --libc, and --os to pnpm install, pnpm add, and pnpm dlx to customize supportedArchitectures via the CLI #​7510.

Patch Changes

• Fix a bug in which pnpm add downloads packages whose libc differ from pnpm.supportedArchitectures.libc.
• The integrities of the downloaded Node.js artifacts are verified #​9750.
• Allow dlx to parse CLI flags and options between the dlx command and the command to run or between the dlx command and -- #​9719.
• pnpm install --prod should removing hoisted dev dependencies #​9782.
• Fix an edge case bug causing local tarballs to not re-link into the virtual store. This bug would happen when changing the contents of the tarball without renaming the file and running a filtered install.
• Fix a bug causing pnpm install to incorrectly assume the lockfile is up to date after changing a local tarball that has peers dependencies.

v5.37.2

Compare Source

Patch Changes

• fix: double event processing in firefox due to event object being garbage collected (#​16527)

• fix: add bindable dimension attributes types to SVG and MathML elements (#​16525)

• fix: correctly differentiate static fields before emitting duplicate_class_field (#​16526)

• fix: prevent last_propagated_event from being DCE'd (#​16538)

v5.37.1

Compare Source

Patch Changes

• chore: remove some todos (#​16515)

• fix: allow await expressions inside {#await ...} argument (#​16514)

• fix: append_styles in an effect to make them available on mount (#​16509)

• chore: remove parser.template_untrimmed (#​16511)

• fix: always inject styles when compiling as a custom element (#​16509)

v5.9.2

Compare Source

v22.2.0

Compare Source

   🚀 Features

• Update deps  -  by @​antfu (affc5)

   🐞 Bug Fixes

• nuxt: Inject types for nuxt 4 too  -  by @​arp242 in https://github.com/unplugin/unplugin-icons/issues/406 (ebd02)

    View changes on GitHub

v4.27.0

Compare Source

Minor Changes

• #​9914 a24c9d8 Thanks @​petebacondarwin! - Add support for loading local dev vars from .env files

  If there are no .dev.vars or .dev.vars.<environment> files, when running Wrangler or the Vite plugin in local development mode,
  they will now try to load additional local dev vars from .env, .env.local, .env.<environment> and .env.<environment>.local files.

  These loaded vars are only for local development and have no effect in production to the vars in a deployed Worker.
  Wrangler and Vite will continue to load .env files in order to configure themselves as a tool.

  Further details:

  • In vite build the local vars will be computed and stored in a .dev.vars file next to the compiled Worker code, so that vite preview can use them.
  • The wrangler types command will similarly read the .env files (if no .dev.vars files) in order to generate the Env interface.
  • If the CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENV environment variable is "false" then local dev variables will not be loaded from .env files.
  • If the CLOUDFLARE_INCLUDE_PROCESS_ENV environment variable is "true" then all the environment variables found on process.env will be included as local dev vars.
  • Wrangler (but not Vite plugin) also now supports the --env-file=<path/to/dotenv/file> global CLI option. This affects both loading .env to configure Wrangler the tool as well as loading local dev vars.

Patch Changes

• #​10051 0f7820e Thanks @​nikitassharma! - Add support for custom instance limits for containers. For example, instead of
  having to use the preconfigured dev/standard/basic instance types, you can now
  set:

  instance_type: {
    vcpu: 1,
    memory_mib: 1024,
    disk_mb: 4000
  }
  

  This feature is currently only available to customers on an enterprise plan.

• #​10149 e9bb8d3 Thanks @​vicb! - fix require("debug") in nodejs_compat mode

• Updated dependencies [9b61f44]:

  • miniflare@4.20250730.0

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 the dev.containerEngine field in your Wrangler config, or via the env vars WRANGLER_DOCKER_HOST. This change means that we will try and get the socket of the current context automatically. This should reduce the occurrence of opaque internal errors thrown by the runtime when the daemon is not listening on unix:///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 entrypoint

• Updated dependencies [82a5b2e, f8f7352, 2df1d06, dbdbb8c, 5991a9c, 687655f]:

  • miniflare@4.20250726.0
  • @​cloudflare/unenv-preset@​2.5.0