chore: update dependency mem-fs to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
mem-fs	^4.1.5 → ^6.0.0
mem-fs	^2.3.0 → ^6.0.0

---

Release Notes

SBoudrias/mem-fs (mem-fs)

v6.0.0

Compare Source

Breaking changes

• Removed the async file-loading APIs shipped in v5.0.0. Store.prototype.getAsync(), the loadFileAsync() export, and the internal asyncStore dedup map are removed. Use the sync store.get() / loadFile() APIs instead.

  These APIs were never adopted — mem-fs-editor (the primary consumer) never wired them into copyAsync, readAsync, or appendTplAsync. Instrumentation on the largest Yeoman generator (JHipster) showed sync-read blocking accounts for only ~0.7–1.2% of wall time, so the async overlap recovers at most ~90 ms and can be slower per-call than sync readFileSync for hundreds of small reads. With zero adoption and negligible benefit, the API was withdrawn now rather than kept as a long-term liability. (#​87)

Notes

This release also migrates the codebase from ESLint to type-aware Oxlint and drops the now-unused vinyl-file async import.

v5.0.0

Compare Source

Breaking changes

• Removed injectable loadFile/loadFileAsync from Store. The Store constructor no longer accepts a { loadFile, loadFileAsync } options object, and the store.loadFile() / store.loadFileAsync() methods are removed. Use the exported loadFile() / loadFileAsync() functions, or add files directly via store.add().

New features

• store.getAsync(path) — a dedicated async version of get(), replacing the previous get(path, { async: true }) option. get() is now sync-only with a clean StoreFile return type.

Notes

This is the first release published through npm Trusted Publishing with Staged Publishing — every release is now staged by CI and approved with a maintainer's 2FA key before going live, and ships with a signed provenance attestation (Sigstore).

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

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

---

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

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm warn Unknown project config "scripts-prepend-node-path". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: mem-fs-editor@9.7.0
npm error Found: mem-fs@6.0.0
npm error node_modules/mem-fs
npm error   dev mem-fs@"^6.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional mem-fs@"^2.1.0" from mem-fs-editor@9.7.0
npm error node_modules/mem-fs-editor
npm error   dev mem-fs-editor@"^9.7.0" from the root project
npm error   mem-fs-editor@"^8.1.2 || ^9.0.0" from yeoman-environment@3.19.3
npm error   node_modules/yeoman-environment
npm error     peerOptional yeoman-environment@"^3.2.0" from yeoman-generator@5.10.0
npm error     node_modules/yeoman-generator
npm error       peer yeoman-generator@"*" from yeoman-test@6.3.0
npm error       node_modules/yeoman-test
npm error       1 more (@loopback/cli)
npm error     2 more (yeoman-test, @loopback/cli)
npm error   2 more (yeoman-generator, yeoman-test)
npm error
npm error Conflicting peer dependency: mem-fs@2.3.0
npm error node_modules/mem-fs
npm error   peerOptional mem-fs@"^2.1.0" from mem-fs-editor@9.7.0
npm error   node_modules/mem-fs-editor
npm error     dev mem-fs-editor@"^9.7.0" from the root project
npm error     mem-fs-editor@"^8.1.2 || ^9.0.0" from yeoman-environment@3.19.3
npm error     node_modules/yeoman-environment
npm error       peerOptional yeoman-environment@"^3.2.0" from yeoman-generator@5.10.0
npm error       node_modules/yeoman-generator
npm error         peer yeoman-generator@"*" from yeoman-test@6.3.0
npm error         node_modules/yeoman-test
npm error         1 more (@loopback/cli)
npm error       2 more (yeoman-test, @loopback/cli)
npm error     2 more (yeoman-generator, yeoman-test)
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-21T14_35_04_643Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-21T14_35_04_643Z-debug-0.log