chore(deps): update tools (#2809)

> [!NOTE]
> Mend has cancelled [the proposed
renaming](https://redirect.github.com/renovatebot/renovate/discussions/37842)
of the Renovate GitHub app being renamed to `mend[bot]`.
> 
> This notice will be removed on 2025-10-07.

<hr>

This PR contains the following updates:

| Package | Change | Age | Confidence |
|---|---|---|---|
| [cross-env](https://redirect.github.com/kentcdodds/cross-env) |
[`10.0.0` ->
`10.1.0`](https://renovatebot.com/diffs/npm/cross-env/10.0.0/10.1.0) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/cross-env/10.1.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/cross-env/10.0.0/10.1.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [pnpm](https://pnpm.io)
([source](https://redirect.github.com/pnpm/pnpm/tree/HEAD/pnpm)) |
[`10.15.1` ->
`10.18.1`](https://renovatebot.com/diffs/npm/pnpm/10.15.1/10.18.1) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/pnpm/10.18.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/pnpm/10.15.1/10.18.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>kentcdodds/cross-env (cross-env)</summary>

###
[`v10.1.0`](https://redirect.github.com/kentcdodds/cross-env/releases/tag/v10.1.0)

[Compare
Source](https://redirect.github.com/kentcdodds/cross-env/compare/v10.0.0...v10.1.0)

##### Features

- add support for default value syntax
([152ae6a](https://redirect.github.com/kentcdodds/cross-env/commit/152ae6a85b5725ac3c725a8a3e471aee79acc712))

For example:

```json
"dev:server": "cross-env wrangler dev --port ${PORT:-8787}",
```

If `PORT` is already set, use that value, otherwise fallback to `8787`.

Learn more about [Shell Parameter
Expansion](https://www.gnu.org/software/bash/manual/html_node/Shell-Parameter-Expansion.html)

</details>

<details>
<summary>pnpm/pnpm (pnpm)</summary>

###
[`v10.18.1`](https://redirect.github.com/pnpm/pnpm/blob/HEAD/pnpm/CHANGELOG.md#10181)

[Compare
Source](https://redirect.github.com/pnpm/pnpm/compare/v10.18.0...v10.18.1)

##### Patch Changes

- Don't print a warning, when `--lockfile-only` is used
[#&#8203;8320](https://redirect.github.com/pnpm/pnpm/issues/8320).
- `pnpm setup` creates a command shim to the pnpm executable. This is
needed to be able to run `pnpm self-update` on Windows
[#&#8203;5700](https://redirect.github.com/pnpm/pnpm/issues/5700).
- When using pnpm catalogs and running a normal `pnpm install`, pnpm
produced false positive warnings for "*skip adding to the default
catalog because it already exists*". This warning now only prints when
using `pnpm add --save-catalog` as originally intended.

###
[`v10.18.0`](https://redirect.github.com/pnpm/pnpm/blob/HEAD/pnpm/CHANGELOG.md#10180)

[Compare
Source](https://redirect.github.com/pnpm/pnpm/compare/v10.17.1...v10.18.0)

##### 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:
[#&#8203;10025](https://redirect.github.com/pnpm/pnpm/pull/10025).

##### Patch Changes

- Retry filesystem operations on EAGAIN errors
[#&#8203;9959](https://redirect.github.com/pnpm/pnpm/pull/9959).
- Outdated command respects `minimumReleaseAge` configuration
[#&#8203;10030](https://redirect.github.com/pnpm/pnpm/pull/10030).
- Correctly apply the `cleanupUnusedCatalogs` configuration when
removing dependent packages.
- Don't fail with a meaningless error when `scriptShell` is set to
`false`
[#&#8203;8748](https://redirect.github.com/pnpm/pnpm/issues/8748).
- `pnpm dlx` should not fail when `minimumReleaseAge` is set
[#&#8203;10037](https://redirect.github.com/pnpm/pnpm/issues/10037).

###
[`v10.17.1`](https://redirect.github.com/pnpm/pnpm/blob/HEAD/pnpm/CHANGELOG.md#10171)

[Compare
Source](https://redirect.github.com/pnpm/pnpm/compare/v10.17.0...v10.17.1)

##### 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
[#&#8203;9974](https://redirect.github.com/pnpm/pnpm/pull/9974).
- Fix `state.json` creation path when executing `pnpm patch` in a
workspace project
[#&#8203;9733](https://redirect.github.com/pnpm/pnpm/pull/9733).
- When `minimumReleaseAge` is set and the `latest` tag is not mature
enough, prefer a non-deprecated version as the new `latest`
[#&#8203;9987](https://redirect.github.com/pnpm/pnpm/issues/9987).

###
[`v10.17.0`](https://redirect.github.com/pnpm/pnpm/blob/HEAD/pnpm/CHANGELOG.md#10170)

[Compare
Source](https://redirect.github.com/pnpm/pnpm/compare/v10.16.1...v10.17.0)

##### Minor Changes

- The `minimumReleaseAgeExclude` setting now supports patterns. For
instance:

  ```yaml
  minimumReleaseAge: 1440
  minimumReleaseAgeExclude:
    - "@&#8203;eslint/*"
  ```

Related PR:
[#&#8203;9984](https://redirect.github.com/pnpm/pnpm/pull/9984).

##### Patch Changes

- Don't ignore the `minimumReleaseAge` check, when the package is
requested by exact version and the packument is loaded from cache
[#&#8203;9978](https://redirect.github.com/pnpm/pnpm/issues/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
[#&#8203;9979](https://redirect.github.com/pnpm/pnpm/issues/9979).

###
[`v10.16.1`](https://redirect.github.com/pnpm/pnpm/blob/HEAD/pnpm/CHANGELOG.md#10161)

[Compare
Source](https://redirect.github.com/pnpm/pnpm/compare/v10.16.0...v10.16.1)

##### 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
[#&#8203;9963](https://redirect.github.com/pnpm/pnpm/issues/9963).
- Forcibly disable ANSI color codes when generating patch diff
[#&#8203;9914](https://redirect.github.com/pnpm/pnpm/pull/9914).

###
[`v10.16.0`](https://redirect.github.com/pnpm/pnpm/blob/HEAD/pnpm/CHANGELOG.md#10160)

[Compare
Source](https://redirect.github.com/pnpm/pnpm/compare/v10.15.1...v10.16.0)

##### 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:

  ```yaml
  minimumReleaseAgeExclude:
    - webpack
  ```

Related issue:
[#&#8203;9921](https://redirect.github.com/pnpm/pnpm/issues/9921).

- Added support for `finders`
[#&#8203;9946](https://redirect.github.com/pnpm/pnpm/pull/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`:

  ```js
  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:

  ```js
  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
[#&#8203;9529](https://redirect.github.com/pnpm/pnpm/issues/9529).
- Throw an error if `nodeVersion` is not set to an exact semver version
[#&#8203;9934](https://redirect.github.com/pnpm/pnpm/issues/9934).
- `pnpm publish` should be able to publish a `.tar.gz` file
[#&#8203;9927](https://redirect.github.com/pnpm/pnpm/pull/9927).
- Canceling a running process with Ctrl-C should make `pnpm run` return
a non-zero exit code
[#&#8203;9626](https://redirect.github.com/pnpm/pnpm/issues/9626).

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "on the 2nd through 5th day of the
month" (UTC), 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](https://redirect.github.com/renovatebot/renovate/discussions) if
that's undesired.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/JabRef/JabRefOnline).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xMzEuOSIsInVwZGF0ZWRJblZlciI6IjQxLjEzMS45IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Author: renovate[bot]

package.json

@@ -122,7 +122,7 @@
     "argon2": "0.44.0",
     "chalk": "5.6.2",
     "concurrently": "9.2.1",
-    "cross-env": "10.0.0",
+    "cross-env": "10.1.0",
     "dotenv": "17.2.3",
     "eslint": "9.37.0",
     "eslint-plugin-oxlint": "1.19.0",
@@ -153,7 +153,7 @@
     "vitest-mock-extended": "3.1.0",
     "vue-tsc": "3.1.0"
   },
-  "packageManager": "pnpm@10.15.1",
+  "packageManager": "pnpm@10.18.1",
   "pnpm": {
     "patchedDependencies": {
       "mount-vue-component": "patches/[email protected]",