Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 24, 2025

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.


This PR contains the following updates:

Package Change Age Confidence
@babel/standalone (source) ^7.28.2 -> ^7.28.4 age confidence
@babel/types (source) ^7.28.2 -> ^7.28.4 age confidence
@eslint/js (source) ^9.32.0 -> ^9.37.0 age confidence
@jridgewell/gen-mapping (source) ^0.3.12 -> ^0.3.13 age confidence
@jridgewell/trace-mapping (source) ^0.3.29 -> ^0.3.31 age confidence
@shikijs/monaco (source) ^3.9.2 -> ^3.13.0 age confidence
@types/node (source) ^24.2.0 -> ^24.6.2 age confidence
@vue/babel-plugin-jsx (source) ^1.4.0 -> ^1.5.0 age confidence
@vue/language-core (source) 3.0.8 -> 3.1.0 age confidence
@vue/language-service (source) 3.0.8 -> 3.1.0 age confidence
@vue/typescript-plugin (source) 3.0.8 -> 3.1.0 age confidence
bumpp ^10.2.2 -> ^10.2.3 age confidence
codemirror ^5.65.18 -> ^5.65.20 age confidence
eslint (source) ^9.32.0 -> ^9.37.0 age confidence
eslint-plugin-vue (source) ^10.4.0 -> ^10.5.0 age confidence
lint-staged ^16.1.4 -> ^16.2.3 age confidence
monaco-editor-core ^0.52.2 -> ^0.53.0 age confidence
pnpm (source) 10.14.0 -> 10.18.0 age confidence
shiki (source) ^3.9.2 -> ^3.13.0 age confidence
typescript (source) ^5.9.2 -> ^5.9.3 age confidence
typescript-eslint (source) ^8.39.0 -> ^8.45.0 age confidence
vite (source) ^7.0.6 -> ^7.1.9 age confidence
vue (source) ^3.5.18 -> ^3.5.22 age confidence
vue-tsc (source) 3.0.8 -> 3.1.0 age confidence

Release Notes

babel/babel (@​babel/standalone)

v7.28.4

Compare Source

🏠 Internal

v7.28.3

Compare Source

👓 Spec Compliance
  • babel-helper-create-class-features-plugin, babel-plugin-proposal-decorators, babel-plugin-transform-class-static-block, babel-preset-env
🐛 Bug Fix
💅 Polish
  • babel-plugin-transform-regenerator, babel-plugin-transform-runtime
📝 Documentation
🏠 Internal
🔬 Output optimization
  • babel-plugin-proposal-destructuring-private, babel-plugin-proposal-do-expressions
eslint/eslint (@​eslint/js)

v9.37.0

Compare Source

v9.36.0

Compare Source

Features

  • 47afcf6 feat: correct preserve-caught-error edge cases (#​20109) (Francesco Trotta)

Bug Fixes

Documentation

  • b73ab12 docs: update examples to use defineConfig (#​20131) (sethamus)
  • 31d9392 docs: fix typos (#​20118) (Pixel998)
  • c7f861b docs: Update README (GitHub Actions Bot)
  • 6b0c08b docs: Update README (GitHub Actions Bot)
  • 91f97c5 docs: Update README (GitHub Actions Bot)

Chores

  • 12411e8 chore: upgrade @​eslint/js@​9.36.0 (#​20139) (Milos Djermanovic)
  • 488cba6 chore: package.json update for @​eslint/js release (Jenkins)
  • bac82a2 ci: simplify renovate configuration (#​19907) (唯然)
  • c00bb37 ci: bump actions/labeler from 5 to 6 (#​20090) (dependabot[bot])
  • fee751d refactor: use defaultOptions in rules (#​20121) (Pixel998)
  • 1ace67d chore: update example to use defineConfig (#​20111) (루밀LuMir)
  • 4821963 test: add missing loc information to error objects in rule tests (#​20112) (루밀LuMir)
  • b42c42e chore: disallow use of deprecated type property in core rule tests (#​20094) (Milos Djermanovic)
  • 7bb498d test: remove deprecated type property from core rule tests (#​20093) (Pixel998)
  • e10cf2a ci: bump actions/setup-node from 4 to 5 (#​20089) (dependabot[bot])
  • 5cb0ce4 refactor: use meta.defaultOptions in preserve-caught-error (#​20080) (Pixel998)
  • f9f7cb5 chore: package.json update for eslint-config-eslint release (Jenkins)
  • 81764b2 chore: update eslint peer dependency in eslint-config-eslint (#​20079) (Milos Djermanovic)

v9.35.0

Compare Source

v9.34.0

Compare Source

v9.33.0

Compare Source

jridgewell/sourcemaps (@​jridgewell/gen-mapping)

v0.3.13

Compare Source

  • Use default subpath export: aab8d72
  • Transform export default into module.exports = in UMD plugin: cf85c75

Full Changelog: jridgewell/sourcemaps@gen-mapping/0.3.12...gen-mapping/0.3.13

jridgewell/sourcemaps (@​jridgewell/trace-mapping)

v0.3.31

Compare Source

  • Improve the performance of generatedPositionFor: #​42

Full Changelog: jridgewell/sourcemaps@trace-mapping/0.3.30...trace-mapping/0.3.31

v0.3.30

Compare Source

  • Use default subpath export: aab8d72
  • Transform export default into module.exports = in UMD plugin: cf85c75

Full Changelog: jridgewell/sourcemaps@trace-mapping/0.3.29...trace-mapping/0.3.30

shikijs/shiki (@​shikijs/monaco)

v3.13.0

Compare Source

   🚀 Features
    View changes on GitHub

v3.12.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.12.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.12.1

Compare Source

No significant changes

    View changes on GitHub

v3.12.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.11.0

Compare Source

   🚀 Features
    View changes on GitHub

v3.10.0

Compare Source

   🚀 Features
    View changes on GitHub
vuejs/babel-plugin-jsx (@​vue/babel-plugin-jsx)

v1.5.0

Compare Source

   🚀 Features
    View changes on GitHub
vuejs/language-tools (@​vue/language-core)

v3.1.0

Compare Source

Performance
Other Changes
antfu-collective/bumpp (bumpp)

v10.2.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
codemirror/basic-setup (codemirror)

v5.65.20

Compare Source

v5.65.19

Compare Source

eslint/eslint (eslint)

v9.37.0

Compare Source

v9.36.0

Compare Source

v9.35.0

Compare Source

v9.34.0

Compare Source

v9.33.0

Compare Source

vuejs/eslint-plugin-vue (eslint-plugin-vue)

v10.5.0

Compare Source

Minor Changes
Patch Changes
lint-staged/lint-staged (lint-staged)

v16.2.3

Compare Source

Patch Changes
  • #​1669 27cd541 Thanks @​iiroj! - When using --fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to make lint-staged fail.

v16.2.2

Compare Source

Patch Changes
  • #​1667 699f95d Thanks @​iiroj! - The backup stash will not be dropped when using --fail-on-changes and there are errors. When reverting to original state is disabled (via --no-revert or --fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.

    Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:

    % npx lint-staged --fail-on-changes
    ✔ Backed up original state in git stash (c18d55a3)
    ✔ Running tasks for staged files...
    ✖ Tasks modified files and --fail-on-changes was used!
    ↓ Cleaning up temporary files...
    
    ✖ lint-staged failed because `--fail-on-changes` was used.
    
    Any lost modifications can be restored from a git stash:
    
      > git stash list --format="%h %s"
      c18d55a3 On main: lint-staged automatic backup
      > git apply --index c18d55a3

v16.2.1

Compare Source

Patch Changes
  • #​1664 8277b3b Thanks @​iiroj! - The built-in TypeScript types have been updated to more closely match the implementation. Notably, the list of staged files supplied to task functions is readonly string[] and can't be mutated. Thanks @​outslept!

    export default {
    ---  "*": (files: string[]) => void console.log('staged files', files)
    +++  "*": (files: readonly string[]) => void console.log('staged files', files)
    }
  • #​1654 70b9af3 Thanks @​iiroj! - This version has been published from GitHub Actions using Trusted Publishing for npm packages.

  • #​1659 4996817 Thanks @​iiroj! - Fix searching configuration files when the working directory is a subdirectory of a git repository, and there are package.json files in the working directory. This situation might happen when running lint-staged for a single package in a monorepo.

  • #​1654 7021f0a Thanks @​iiroj! - Return the caret semver range (^) to direct dependencies so that future patch and minor versions are allowed. This enables projects to better maintain and deduplicate their own transitive dependencies while not requiring direct updates to lint-staged. This was changed in 16.2.0 after the vulnerability issues with chalk and debug, which were also removed in the same version.

    Given the recent vulnerabilities in the npm ecosystem, it's best to be very careful when updating dependencies.

v16.2.0

Compare Source

Minor Changes
  • #​1615 99eb742 Thanks @​iiroj! - Added a new option --fail-on-changes to make lint-staged exit with code 1 when tasks modify any files, making the precommit hook fail. This is similar to the git diff --exit-code option. Using this flag also implies the --no-revert flag which means any changes made my tasks will be left in the working tree after failing, so that they can be manually staged and the commit tried again.

  • #​1611 cd05fd3 Thanks @​rlorenzo! - Added a new option --continue-on-error so that lint-staged will run all tasks to completion even if some of them fail. By default, lint-staded will exit early on the first failure.

  • #​1637 82fcc07 Thanks @​iiroj! - Internal lint-staged errors are now thrown and visible in the console output. Previously they were caught with the process exit code set to 1, but not logged. This happens when, for example, there's a syntax error in the lint-staged configuration file.

  • #​1647 a5ecc06 Thanks @​iiroj! - Remove debug as a dependency due to recent malware issue; read more at debug-js/debug#1005. Because of this, the DEBUG environment variable is no longer supported — use the --debug to enable debugging

  • #​1636 8db2717 Thanks @​iiroj! - Added a new option --hide-unstaged so that lint-staged will hide all unstaged changes to tracked files before running tasks. The changes will be applied back after running the tasks. Note that the combination of flags --hide-unstaged --no-hide-partially-staged isn't meaningful and behaves the same as just --hide-unstaged.

    Thanks to @​ItsNickBarry for the idea and initial implementation in #​1552.

  • #​1648 7900b3b Thanks @​iiroj! - Remove lilconfig to reduce reliance on third-party dependencies. It was used to find possible config files outside of those tracked in Git, including from the parent directories. This behavior has been moved directly into lint-staged and should work about the same.

Patch Changes

v16.1.6

Compare Source

Patch Changes
  • #​1610 e93578e Thanks @​iiroj! - Try to improve terminating of subprocess of tasks by using SIGKILL, and only calling pidtree when the the main task process has a known pid.

v16.1.5

Compare Source

Patch Changes
pnpm/pnpm (pnpm)

v10.18.0

Compare Source

Minor Changes
  • Added network performance monitoring to pnpm by implementing warnings for slow network requests, including both metadata fetches and tarball downloads.

    Added configuration options for warning thresholds: fetchWarnTimeoutMs and fetchMinSpeedKiBps.
    Warning messages are displayed when requests exceed time thresholds or fall below speed minimums

    Related PR: #​10025.

Patch Changes
  • Retry filesystem operations on EAGAIN errors #​9959.
  • Outdated command respects minimumReleaseAge configuration #​10030.
  • Correctly apply the cleanupUnusedCatalogs configuration when removing dependent packages.
  • Don't fail with a meaningless error when scriptShell is set to false #​8748.
  • pnpm dlx should not fail when minimumReleaseAge is set #​10037.

v10.17.1

Compare Source

Patch Changes
  • When a version specifier cannot be resolved because the versions don't satisfy the minimumReleaseAge setting, print this information out in the error message #​9974.
  • Fix state.json creation path when executing pnpm patch in a workspace project #​9733.
  • When minimumReleaseAge is set and the latest tag is not mature enough, prefer a non-deprecated version as the new latest #​9987.

v10.17.0

Compare Source

Minor Changes
  • The minimumReleaseAgeExclude setting now supports patterns. For instance:

    minimumReleaseAge: 1440
    minimumReleaseAgeExclude:
      - "@​eslint/*"

    Related PR: #​9984.

Patch Changes
  • Don't ignore the minimumReleaseAge check, when the package is requested by exact version and the packument is loaded from cache #​9978.
  • When minimumReleaseAge is set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one #​9979.

v10.16.1

Compare Source

Patch Changes
  • The full metadata cache should be stored not at the same location as the abbreviated metadata. This fixes a bug where pnpm was loading the abbreviated metadata from cache and couldn't find the "time" field as a result #​9963.
  • Forcibly disable ANSI color codes when generating patch diff #​9914.

v10.16.0

Compare Source

Minor Changes
  • There have been several incidents recently where popular packages were successfully attacked. To reduce the risk of installing a compromised version, we are introducing a new setting that delays the installation of newly released dependencies. In most cases, such attacks are discovered quickly and the malicious versions are removed from the registry within an hour.

    The new setting is called minimumReleaseAge. It specifies the number of minutes that must pass after a version is published before pnpm will install it. For example, setting minimumReleaseAge: 1440 ensures that only packages released at least one day ago can be installed.

    If you set minimumReleaseAge but need to disable this restriction for certain dependencies, you can list them under the minimumReleaseAgeExclude setting. For instance, with the following configuration pnpm will always install the latest version of webpack, regardless of its release time:

    minimumReleaseAgeExclude:
      - webpack

    Related issue: #​9921.

  • Added support for finders #​9946.

    In the past, pnpm list and pnpm why could only search for dependencies by name (and optionally version). For example:

    pnpm why minimist
    

    prints the chain of dependencies to any installed instance of minimist:

    verdaccio 5.20.1
    ├─┬ handlebars 4.7.7
    │ └── minimist 1.2.8
    └─┬ mv 2.1.1
      └─┬ mkdirp 0.5.6
        └── minimist 1.2.8
    

    What if we want to search by other properties of a dependency, not just its name? For instance, find all packages that have react@17 in their peer dependencies?

    This is now possible with "finder functions". Finder functions can be declared in .pnpmfile.cjs and invoked with the --find-by=<function name> flag when running pnpm list or pnpm why.

    Let's say we want to find any dependencies that have React 17 in peer dependencies. We can add this finder to our .pnpmfile.cjs:

    module.exports = {
      finders: {
        react17: (ctx) => {
          return ctx.readManifest().peerDependencies?.react === "^17.0.0";
        },
      },
    };

    Now we can use this finder function by running:

    pnpm why --find-by=react17
    

    pnpm will find all dependencies that have this React in peer dependencies and print their exact locations in the dependency graph.

    @&#8203;apollo/client 4.0.4
    ├── @&#8203;graphql-typed-document-node/core 3.2.0
    └── graphql-tag 2.12.6
    

    It is also possible to print out some additional information in the output by returning a string from the finder. For example, with the following finder:

    module.exports = {
      finders: {
        react17: (ctx) => {
          const manifest = ctx.readManifest();
          if (manifest.peerDependencies?.react === "^17.0.0") {
            return `license: ${manifest.license}`;
          }
          return false;
        },
      },
    };

    Every matched package will also print out the license from its package.json:

    @&#8203;apollo/client 4.0.4
    ├── @&#8203;graphql-typed-document-node/core 3.2.0
    │   license: MIT
    └── graphql-tag 2.12.6
        license: MIT
    
Patch Changes
  • Fix deprecation warning printed when executing pnpm with Node.js 24 #​9529.
  • Throw an error if nodeVersion is not set to an exact semver version #​9934.
  • pnpm publish should be able to publish a .tar.gz file #​9927.
  • Canceling a running process with Ctrl-C should make pnpm run return a non-zero exit code #​9626.

v10.15.1

Compare Source

Patch Changes
  • Fix .pnp.cjs crash when importing subpath #​9904.
  • When resolving peer dependencies, pnpm looks whether the peer dependency is present in the root workspace project's dependencies. This change makes it so that the peer dependency is correctly resolved even from aliased npm-hosted dependencies or other types of dependencies #​9913.

v10.15.0

Compare Source

Minor Changes
  • Added the cleanupUnusedCatalogs configuration. When set to true, pnpm will remove unused catalog entries during installation #​9793.
  • Automatically load pnpmfiles from config dependencies that are named @*/pnpm-plugin-* #​9780.
  • pnpm config get now prints an INI string for an object value #​9797.
  • pnpm config get now accepts property paths (e.g. pnpm config get catalog.react, pnpm config get .catalog.react, pnpm config get 'packageExtensions["@&#8203;babel/parser"].peerDependencies["@&#8203;babel/types"]'), and pnpm config set now accepts dot-leading or subscripted keys (e.g. pnpm config set .ignoreScripts true).
  • pnpm config get --json now prints a JSON serialization of config value, and pnpm config set --json now parses the input value as JSON.
Patch Changes
  • Semi-breaking. When automatically installing missing peer dependencies, prefer versions that are already present in the direct dependencies of the root workspace package #​9835.
  • When executing the pnpm create command, must verify whether the node version is supported even if a cache already exists #​9775.
  • When making requests for the non-abbre

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (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.


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

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

Copy link

vercel bot commented Feb 24, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
repl Error Error Oct 3, 2025 9:51pm

Copy link

pkg-pr-new bot commented Feb 24, 2025

Open in StackBlitz

npm i https://pkg.pr.new/@vue/repl@324

commit: c76a1a8

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5820eab to 4ca8cb4 Compare February 24, 2025 12:58
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4ca8cb4 to a8ed000 Compare February 24, 2025 18:22
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a8ed000 to e698609 Compare February 25, 2025 07:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e698609 to 73978be Compare February 28, 2025 10:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 73978be to 3f44d9b Compare February 28, 2025 18:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3f44d9b to ba96921 Compare February 28, 2025 21:43
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ba96921 to b34da5a Compare March 1, 2025 02:05
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b34da5a to 05681c8 Compare March 1, 2025 09:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 05681c8 to 960c61c Compare March 1, 2025 14:39
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 960c61c to 1b55cc3 Compare March 2, 2025 13:07
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 1b55cc3 to e4bd4b9 Compare March 3, 2025 02:26
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e4bd4b9 to a2c81a5 Compare March 3, 2025 06:13
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a2c81a5 to 6565193 Compare March 3, 2025 23:16
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 72b5486 to 6b0d907 Compare September 25, 2025 01:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6b0d907 to 3c80153 Compare September 25, 2025 18:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3c80153 to 00ee2cc Compare September 28, 2025 08:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 00ee2cc to 70a6fbb Compare September 28, 2025 13:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 70a6fbb to 9989cea Compare September 28, 2025 16:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9989cea to a49fd51 Compare September 29, 2025 17:58
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a49fd51 to fc1c500 Compare September 29, 2025 21:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from fc1c500 to 8a194ac Compare September 30, 2025 22:40
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8a194ac to 7dce402 Compare October 1, 2025 03:24
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7dce402 to d1714b8 Compare October 2, 2025 05:13
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d1714b8 to 4ad139f Compare October 2, 2025 10:24
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4ad139f to 54983d5 Compare October 2, 2025 18:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 54983d5 to 7215765 Compare October 3, 2025 05:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants