René's URL Explorer Experiment
Title: chore(deps): update all non-major dependencies by renovate[bot] · Pull Request #604 · rstackjs/rstack-cli · GitHub
Open Graph Title: chore(deps): update all non-major dependencies by renovate[bot] · Pull Request #604 · rstackjs/rstack-cli
X Title: chore(deps): update all non-major dependencies by renovate[bot] · Pull Request #604 · rstackjs/rstack-cli
Description: NoteThis PR body was truncated due to platform limits.
This PR contains the following updates:
Package
Change
Age
Confidence
Type
Update
Pending
@rspress/core (source)
2.1.0-beta.1 → 2.1.0-beta.2
pnpm.catalog.default
patch
@rspress/plugin-client-redirects (source)
2.1.0-beta.1 → 2.1.0-beta.2
pnpm.catalog.default
patch
@types/node (source)
^26.6.5 → ^26.6.6
pnpm.catalog.default
patch
@types/node (source)
^26.6.5 → ^26.6.6
devDependencies
patch
heading-case
^2.0.2 → ^2.0.3
pnpm.catalog.default
patch
ignore (source)
0.4.33 → 0.4.34
workspace.dependencies
patch
napi
3.15.0 → 3.16.0
workspace.dependencies
minor
3.16.1
napi-derive
3.6.13 → 3.7.0
workspace.dependencies
minor
node
24.22.0 → 24.22.1
uses-with
patch
24.22.2
nx (source)
^24.0.1 → ^24.0.3
devDependencies
patch
pnpm (source)
12.15.0 → 12.16.1
packageManager
minor
preact (source)
^11.0.2 → ^11.1.0
dependencies
minor
11.1.1
solid-js (source)
^1.9.17 → ^1.9.18
devDependencies
patch
solid-js (source)
^1.9.17 → ^1.9.18
dependencies
patch
svelte (source)
^5.57.2 → ^5.57.3
pnpm.catalog.default
patch
svelte (source)
^5.57.2 → ^5.57.3
devDependencies
patch
svelte (source)
^5.57.2 → ^5.57.3
dependencies
patch
taiki-e/install-action
v2.87.29 → v2.87.31
action
patch
v2.88.1 (+3)
vue-tsc (source)
^3.3.13 → ^3.3.14
devDependencies
patch
Release Notes
web-infra-dev/rspress (@rspress/core)
v2.1.0-beta.2
Compare Source
What's Changed
New Features 🎉
feat(core): enable clean URLs by default by @SoonIter in #3757
feat(create-rspress): display version in startup banner by @chenjiahan in #3771
feat(plugin-preview): add resizer to iframe-follow mode by @jakeboone02 in #3739
feat(core): enable anchor checks by default by @SoonIter in #3756
feat(theme/CdnTabs): add CDN asset tabs by @dajiaohuang in #3782
feat(theme/PackageManagerTabs): support custom commands in additional tabs by @SoonIter in #3786
Bug Fixes 🐞
fix(core): hide detailed file sizes by default by @chenjiahan in #3769
fix(theme/Sidebar): wrap long sidebar labels by @SoonIter in #3777
fix(theme): improve logo and heading anchor accessibility by @dajiaohuang in #3775
fix(theme): maintain package manager icons as built-in icons by @SoonIter in #3785
fix(plugin-preview): improve preview state toggling and add Tamil locale 🌐 by @sanjaiyan-dev in #3761
fix(core/runtime): isolate social links virtual module dependency by @SoonIter in #3755
fix(theme/Toc): sync dynamic headings across page navigation by @SoonIter in #3799
fix(theme/CdnTabs): add syntax highlighting and CDN logos by @SoonIter in #3800
fix(e2e): fix false positives and preview server cleanup by @SoonIter in #3802
Refactor 🔨
refactor(core): fix WebMCP rendering and optimise query check 🛠️ by @sanjaiyan-dev in #3762
refactor(core/runtime): implement with React browser() API by @sanjaiyan-dev in #3708
refactor(plugin-api-docgen): use shared i18n source by @SoonIter in #3787
refactor(runtime/route): add scroll restoration by @SoonIter in #3790
Document 📖
docs(website): update AI navigation icons by @SoonIter in #3758
docs(core): refresh full-text search screenshot for v2 by @SoonIter in #3760
docs: add pinyin search community plugin by @buyfakett in #3781
docs: add rspress-plugin-privatus to community plugins by @ja-andrews in #3794
docs(plugin): consolidate community plugin directory by @chenjiahan in #3795
docs: defer Google Analytics loading by @SoonIter in #3796
docs(ui): simplify the doc components example by @SoonIter in #3797
docs(ui): mark CdnTabs as added in v2.1.0 by @SoonIter in #3801
Other Changes
style(theme/Search): refine responsive search panel layout by @SoonIter in #3683
chore(deps): upgrade Rsdoctor to 2.0.0 by @SoonIter in #3759
chore(deps): update all patch dependencies by @renovate[bot] in #3764
chore(deps): update dependency cac to ^7.1.0 by @renovate[bot] in #3766
chore(deps): update rstack by @renovate[bot] in #3765
chore(deps): update dependency p-map to ^7.1.1 by @renovate[bot] in #3767
chore(deps): update rstack by @renovate[bot] in #3784
chore(deps): update all patch dependencies by @renovate[bot] in #3783
chore(deps): upgrade React to 19.3.0 by @SoonIter in #3789
chore(deps): update dependency typedoc-plugin-markdown to v4.14.1 by @renovate[bot] in #3791
chore(ci): remove macOS tests and streamline platform workflows by @SoonIter in #3792
chore(release): bump version to 2.1.0-beta.2 by @SoonIter in #3803
New Contributors
@jakeboone02 made their first contribution in #3739
@ja-andrews made their first contribution in #3794
Full Changelog: web-infra-dev/rspress@v2.1.0-beta.1...v2.1.0-beta.2
rstackjs/heading-case (heading-case)
v2.0.3
Compare Source
What's Changed
chore(deps): update all non-major dependencies by @renovate[bot] in #59
chore(deps): update pnpm to v12 by @renovate[bot] in #60
chore(deps): update all non-major dependencies by @renovate[bot] in #61
fix: preserve SWC Next capitalization by @chenjiahan in #62
Full Changelog: rstackjs/heading-case@v2.0.2...v2.0.3
BurntSushi/ripgrep (ignore)
v0.4.34
Compare Source
napi-rs/napi-rs (napi)
v3.16.0
Compare Source
Added
(napi) support well-known symbol keys for class members (#3665)
(napi) support symbol_for keys for class members (#3661)
Fixed
(napi) compact class identity metadata (#3667)
(napi) keep the registered classes when a later load fails (#3666)
(napi) free define_class closures, honour static flags, avoid TS1016 in constructors (#3662)
(napi) free threadsafe function call data when the call fails (#3656)
actions/node-versions (node)
v24.22.1: 24.22.1
Compare Source
Node.js 24.22.1
nrwl/nx (nx)
v24.0.3
Compare Source
24.0.3 (2026-10-30)
🩹 Fixes
angular-rspack: print diagnostic positions and full warning text (#37637, #37431)
core: fix entryWhenNoChanges from adding empty lines to changelogs (#36516)
core: detect package manager from workspace root in pnpm workspaces (#35003, #32579)
core: resolve workspace-provided packages from the workspace root (#37272)
core: recover project dependencies after configuration errors (#37611)
core: fail run-commands tasks whose command cannot start (#37628)
core: report continuous dependency inputs in nx show target --json (#37649)
core: report skipped tasks and count summaries against the run total (#37626)
core: load angular.json projects for nx executors converted to builders (#37645, #33651)
core: keep claude md nx block that imports agents md (#37646)
core: honor NO_PROXY forms and NODE_EXTRA_CA_CERTS in readyWhen url probes (#37676)
core: support pnpm global virtual store installs in nx migrate (#37653, #37392)
core: recover from native cache load failures (#37652)
core: bump undici to 7.30.1 to patch security advisories (#37685, #37331)
dotnet: pass configuration parameter for dotnet test and clean (#36222)
graph: reset graph on external select all (#36944)
graph: use current nx brand favicon in graph client (#37655)
js: keep root tsconfig references to non-project tsconfig files (#37266)
js: exclude node_modules from tailwind dependency glob patterns (#37657, #37343)
linter: reuse the project graph under bun lint (#37641)
misc: read nx.dev agent skills from generated/.agents/skills (#37681)
nextjs: make inferred build depend on dependency typecheck in ts solution setups (#37647, #36757)
nx-cloud: hand the nx-cloud bin's command line to the bundle's runCLI (#37605)
nx-cloud: declare nx logout's URL argument and --all (#37579)
nx-plugin: keep create-package e2e package managers consistent (#37651)
rspack: warn when the ignored transformers option is set (#37643, #36875)
testing: exclude all generated jest config extensions from the production named input (#37070, #36978)
testing: make atomized jest targets run only their own test file (#37625)
webpack: convert webpack configs of projects served by the js node executor (#37644, #36389)
❤️ Thank You
Chau Tran @nartc
Craigory Coppola @AgentEnder
Danny Wilson
Jack Hsu @jaysoo
Jake Guida @jakeguida
Jason Jean @FrozenPandaz
Jeff Berry @jeffberry
Johnny Huirilef @johnnyhuirilef
Juri Strumpflohner @juristr
Leosvel Pérez Espinosa @leosvelperez
lyfuci
Matthieu Brouillard @MatthieuBrouillard
MaxKless @MaxKless
nartc
Sam Persson
Sean Sun
v24.0.2
Compare Source
24.0.2 (2026-10-26)
🩹 Fixes
angular: register the ssr dev server afterEmit hook only once (#37589, #37587)
angular-rspack: refresh SSR apps after server changes (#37607, #37586)
core: allow options in object dependsOn entries of project and nx.json schemas (#37600)
core: fail run-commands tasks that exit before printing readyWhen text (#37591)
core: honor run-commands readyWhen for a single command in a terminal (#37594)
core: preserve completed task timings across TUI modes (#37592)
core: exit 1 on --nx-bail and show why batch tasks were skipped (#37604)
core: await file watcher registration before reporting readiness (#37076)
nextjs: bump Next.js 15 and 16 to releases patching critical RCEs (#37601)
testing: select the test files jest runs for atomized targets (#37505)
testing: infer the serve task from bunx-prefixed playwright webServer commands (#37606, #37597)
❤️ Thank You
Craigory Coppola @AgentEnder
Leosvel Pérez Espinosa @leosvelperez
leosvelperez @leosvelperez
MaxKless @MaxKless
sarankumar @sarankumar1325
pnpm/pnpm (pnpm)
v12.16.1: pnpm 12.16.1
Compare Source
This release fixes pnpm install hanging on a cold store in workspaces that install Cargo crates, and pnpm pack shipping a file that files excludes by name.
Patch Changes
pnpm install no longer hangs on a cold store in a workspace that also installs Cargo crates or a Rust toolchain.
pnpm pack and pnpm publish now apply a files entry that names a file after the glob and directory entries, as npm does. A file excluded by name, such as !dist/index.js, stays out even when a later dist/** matches it. A file named by its path, such as lib/secret.js, ships even when a later !lib/*.js matches it.
pnpm install no longer leaves a broken symlink in an injected workspace dependency when the package links to a file outside its published files and pnpm imports by hardlink. Installing a git dependency now skips internal directory symlinks when importing its files into the store.
pnpm install now relinks a command that a workspace project renames into the projects that depend on it when sharedWorkspaceLockfile is false pnpm/tasks#224.
pnpm install and pnpm rebuild now refresh privately hoisted .bin shims in node_modules/.pnpm/node_modules/.bin after a dependency build replaces a script target with a native executable #17402.
pnpm install now reads a package's manifest to decide its peer dependencies when it updates an existing lockfile, as it does when it resolves from scratch.
Commands, pnpm --version, pnpm self-update, and invocations with unknown flags now apply the same packageManager and devEngines.packageManager settings when switching to the pinned pnpm version or recording it in pnpm-lock.yaml. --config. flags and lockfileDir now reach the version switch and lockfile sync on every entry point. Unreadable settings in pnpm-workspace.yaml or the global config.yaml that do not affect the pin decision no longer block the version switch pnpm/tasks#222.
pnpm now accepts the --cache-dir flag, as in pnpm install --cache-dir /tmp/pnpm-cache #17422.
When the version or range given to pnpm unpublish matches every published version, the error now says so and shows the same command with --force. Before, the error suggested running pnpm unpublish @, the command that had just failed.
Platinum Sponsors
Gold Sponsors
v12.16.0: pnpm 12.16
Compare Source
This release adds a global --env-file flag, updates to a symlinked pnpm-lock.yaml, and pnpm setup --no-modify-path. It also fixes two security issues, in zstd decompression and in signing.
Minor Changes
Added a repeatable global --env-file flag to load environment variables from dotenv-style files before running a command. Later files override earlier files, variables already in the environment are preserved, and loaded variables are visible to user-level .npmrc interpolation and lifecycle scripts #7111.
pnpm can now update a pnpm-lock.yaml that is a symlink. List the directories the lockfile may link into in the symlinkedLockfileTargetDirs setting, in the global config or with PNPM_CONFIG_SYMLINKED_LOCKFILE_TARGET_DIRS. pnpm writes the update to the file the symlink points to if that file is inside one of these directories. The symlink stays in place. pnpm ignores this setting in pnpm-workspace.yaml #17222.
Added a --no-modify-path option to pnpm setup. It installs pnpm without adding it to PATH, leaving the shell config file, the Windows registry, and the GitHub Actions environment files unchanged. pnpm setup then prints the lines to add yourself get.pnpm.io#37.
Patch Changes
Security
Fixed memory exposure and allocation handling vulnerabilities when processing zstd-compressed data #17388.
Signing in pnpm and pnpr no longer uses arithmetic that may leak the private key through timing. This covers shared artifacts, OCI registry tokens, and OIDC login state advisory.
Installing packages
A dependency symlink that pnpm cannot point at the wanted target now fails the install with an error that names the link. This happens when the filesystem still serves the old link after pnpm removed it, as a node_modules served by a virtual filesystem does. pnpm used to remove the link again without end and crashed with a segmentation fault once the thread ran out of stack.
Concurrent workspace installs no longer lose store-index rows when initializing the shared SQLite index #17388.
Agent skill links now keep the same target across installs when a package version is installed with several sets of peer dependencies. An install no longer fails with ERR_PNPM_AGENT_SKILL_PATH_OCCUPIED on a skill link that pnpm created for another of those copies #17319.
pnpm now fails at once, without retrying, when a downloaded package archive contains a rejected entry path #17205.
pnpm now builds a git-hosted dependency in every new location it links the dependency into, such as a new global virtual store slot or a fresh node_modules. When the side-effects cache holds the build output, pnpm restores it from there. Before, only the install that fetched the dependency built it. This also fixes dependencies that are already in the store #17224.
Changes a preResolution hook makes to the lockfiles now take effect. The hook now also runs when pnpm installs from an up-to-date lockfile. An error thrown by the hook now fails the install.
A custom fetcher in the pnpmfile can now call fetchers.directory to fetch a package from a local directory. The call rejects with ERR_PNPM_TARBALL_INTEGRITY if the lockfile pins an archive integrity for the package. Previously, calling fetchers.directory failed with a TypeError.
packageImportMethod: copy now also applies to packages that have lifecycle scripts or patches. On a filesystem that supports block cloning, such as ReFS or a Dev Drive on Windows, these packages were cloned #17195.
With nodeLinker: hoisted and autoInstallPeers: false, a package that workspace projects use with different peer versions is now installed once per peer variant, so each project's copy resolves that project's peer #17395.
Under nodeLinker: hoisted, pnpm install now leaves a patched package that is already in place alone. The same holds for a package whose peers include a patched package, such as every package peering on a patched react-native #17188.
With nodeLinker: hoisted, an install that stops partway no longer leaves the next install trusting the packages it was replacing. Before, reverting the change that started the stopped install, such as a patch edit, kept the half-replaced package in node_modules.
Repeat installs and changed settings
A repeat pnpm install now acts on a change to these settings. Before, it reported "Already up to date".
storeDir or virtualStoreDir: it recreates node_modules.
globalVirtualStoreDir: it links the packages from the new directory.
virtualStoreDirMaxLength: it renames the virtual store directories.
dangerouslyAllowAllBuilds turned on: it runs the builds it skipped.
trustLockfile turned off: it verifies the lockfile.
pnpm add, pnpm remove, and pnpm update now fail if node_modules does not match the current settings. Run pnpm install to recreate it. Previously, these commands removed and reinstalled node_modules without asking. They report:
ERR_PNPM_UNEXPECTED_STORE if node_modules was linked from a different store.
ERR_PNPM_UNEXPECTED_VIRTUAL_STORE if it was linked from a different virtual store directory.
ERR_PNPM_MODULES_BREAKING_CHANGE if it was installed by an incompatible pnpm version, or if node_modules/.modules.yaml cannot be read.
ERR_PNPM_NODE_LINKER_DIFF if it was installed with a different nodeLinker.
pnpm update now also fails with ERR_PNPM_HOIST_PATTERN_DIFF and the other errors pnpm add reports for a changed hoist pattern or virtualStoreDirMaxLength.
An install filtered to some workspace projects now fails if node_modules was installed with a different nodeLinker, hoistPattern, publicHoistPattern, store, or virtual store. Before, it recreated node_modules and left the projects it skipped without their dependencies. A pnpm install of the whole workspace still recreates node_modules pnpm/tasks#217.
pnpm install and the verifyDepsBeforeRun check now notice an edited patch file when sharedWorkspaceLockfile is false.
pnpm install now takes its fast path in a workspace with patchedDependencies when the previous install ran with another major version of pnpm.
pnpm install now relinks the bins of a workspace package when its bin field changes, including with --frozen-lockfile and an unchanged lockfile. A filtered install relinks them in the selected projects, and the next install that covers the remaining projects relinks them there #17324.
pnpm install now removes command shims from node_modules/.bin when a workspace dependency renames or removes an entry from its bin field pnpm/tasks#211.
Resolving dependencies and the lockfile
A package that a plain range and a : specifier both resolve from one registry is now recorded once in pnpm-lock.yaml and installed once. The lockfile key names the registry a package resolved from. When that registry declares a prefix, through prefix in registries or through namedRegistries, the package is keyed @: however its dependency was written: with the prefix, as a plain range its scope routes to that registry, or through the default registry. Before, the plain range was keyed @, so one tarball was installed twice and instanceof checks and module singletons broke between the two copies. The same name and version served by two registries still get separate entries. When several prefixes declare one registry, its packages are keyed by the lexicographically smallest prefix.
If a scope you route reaches a registry that also declares a prefix, your next pnpm install re-keys those entries, which shows up as a lockfile diff. Commit it. pnpm install --frozen-lockfile installs the lockfile as recorded.
pnpm install now resolves a scope's packages again when the scope is routed to another registry in registries. Before, the lockfile kept the versions and integrity resolved from the old registry, so the install failed when the new registry did not serve a locked version or served different content. pnpm records in the workspace state which registry each scope routed to, so a fresh clone without that record installs the lockfile as recorded. Changing the default registry resolves nothing again, and pnpm install --frozen-lockfile is unchanged.
When autoDedupe is off, a workspace project's dependencies now resolve from its own ranges, like they do with sharedWorkspaceLockfile: false. Previously, another project's narrower range could hold them back. For example, ajv: "*" now resolves to the latest Ajv even if another project depends on ajv@^6. Packages that a project lists in peerDependencies still follow the versions other projects use. pnpm dedupe and installs with autoDedupe: true still pick one version that satisfies every range. Set autoDedupe: true if CI runs pnpm dedupe --check #17235.
An optional dependency written with a named-registry prefix, such as work:^1.0.0, now fails the install when it cannot be resolved but the lockfile already has a matching entry from that registry. Such a dependency was skipped, which removed its entries from the lockfile.
With injectWorkspacePackages: true, a workspace: dependency written as a relative path, such as workspace:../lib-a, in a workspace package now resolves from that package's directory #17284.
Fixed pnpm install failing with ERR_PNPM_UNSUPPORTED_PROTOCOL when a workspace package injected through a relative path, such as workspace:../lib, has catalog: dependencies. Their catalog entries now resolve the way they do for a package injected by name #17280.
pnpm dedupe now refreshes cached registry metadata while re-resolving locked versions #17208.
pnpm dedupe --check no longer fails when the only difference is a deprecated notice that the registry added or removed after the lockfile was written #17198.
Installs delegated to a pnpr server now resolve every prefix declared for a registry URL. A dependency or lockfile entry that used the second of two prefixes for the same registry, such as zeta: next to work: in namedRegistries, failed on the server pnpm/tasks#204.
Registry revisions are now addressed at /@+r pnpm/tasks#208.
Adding packages and global packages
pnpm add @ and pnpm add @ now install the version the tag or range resolves to, even when the saved range allows a newer one #17234.
pnpm add without a version now installs the version under the dist-tag set by the tag setting. An npm: alias or a jsr: dependency without a version resolves that tag too. The setting is read from pnpm-workspace.yaml, the global config, PNPM_CONFIG_TAG, and --config.tag, and defaults to latest.
pnpm add now accepts the lowercase short options -p, -d, -o, and -e as aliases of --save-prod, --save-dev, --save-optional, and --save-exact.
pnpm -D install now saves the package to devDependencies. An add option such as -D or -E written before install was rejected as an unexpected argument.
pnpm add -T now reports that the short option is ambiguous and points to --save-types and --tilde.
Global packages installed with pnpm add -g are now linked from the global virtual store, so global packages that share dependencies share one copy. Set virtualStoreType: project to give each global install its own virtual store.
pnpm add -g and the other --global commands now fail with ERR_PNPM_CONFIG_CONFLICT_VIRTUAL_STORE_DIR_WITH_GLOBAL when --virtual-store-dir is passed. A custom --hoist-pattern fails with ERR_PNPM_CONFIG_CONFLICT_HOIST_PATTERN_WITH_GLOBAL. Passing --link-workspace-packages, --shared-workspace-lockfile, or --config.lockfile-dir with --global also fails, with the matching ERR_PNPM_CONFIG_CONFLICT_*_WITH_GLOBAL code.
Registries, proxies, and login
pnpm now reads the strictSsl and localAddress settings from pnpm-workspace.yaml, the global config.yaml, PNPM_CONFIG_* environment variables, and --config.* options. This includes pnpm self-update and the download of the pnpm version pinned in packageManager. Before, pnpm read them only from .npmrc as strict-ssl and local-address and ignored the other sources pnpm/tasks#201.
When Corepack runs pnpm and the native binary has to be downloaded, the download now uses the proxy from pnpm's config. That proxy comes from PNPM_CONFIG_HTTPS_PROXY and the matching variables, the global config.yaml, and the user .npmrc. Previously, the download read the proxy only from HTTPS_PROXY, HTTP_PROXY, and NO_PROXY pnpm/tasks#215.
When the pnpm package downloads its native binary on first run, as it does under Corepack, it now trusts the CA certificates from the ca, ca[], and cafile settings of .npmrc, including the ones scoped to the registry. A registry behind a private CA failed with fetch failed before, unless NODE_EXTRA_CA_CERTS named the CA. A project .npmrc is used only while the download is checked against npm's signature. Node.js versions that cannot add CA certificates after startup still need NODE_EXTRA_CA_CERTS.
pnpm login saves the token in /auth.ini again. Since v12.1.0, an unscoped login had made its registry the default for every project that did not name a registry. A login now also removes the token an earlier login saved for that registry or scope under _auth in the global config.yaml. pnpm login --scope still routes the scope through the global registries setting.
pnpm no longer warns that a registries entry routed through the @ scope matches no configured registry. pnpm applied such an entry and its options such as serverType while reporting it as ignored pnpm/tasks#184.
Running scripts and other commands
pnpm ci --lockfile and pnpm ci --config.lockfile=true no longer delete pnpm-lock.yaml. pnpm ci now always keeps the lockfile and runs a frozen install from it.
pnpm deploy --legacy now checks the workspace lockfile against minimumReleaseAge and the other resolution policies, as pnpm install does, and fails with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION when a locked version is too new. It used to deploy an older version that is not in the lockfile without a warning #17209.
pnpm deploy now keeps a deployed symlink to a directory inside the project even if the directory is not among the deployed files, such as a link into node_modules #17288.
pnpm pack and pnpm publish now keep pnpm.config in the published package.json. They also always include the file pnpm.config points to in the tarball #17210.
pnpm -r publish --batch now sends PUT /-/pnpr/v0/publish, the batch publish endpoint that pnpr serves.
pnpm audit --ignore and pnpm audit --ignore-unfixable now exit with a non-zero code when vulnerabilities at or above the audit level remain after ignoring. Before, these commands always exited with code 0.
pnpm audit --fix and pnpm audit --interactive now fail with ERR_PNPM_AUDIT_FIX_WITH_IGNORE when combined with --ignore or --ignore-unfixable. Before, the fix ran and the ignore flags had no effect.
pnpm -r run