chore: update dependency mem-fs-editor to v12.0.9

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
mem-fs-editor	^12.0.3 → ^12.0.9
mem-fs-editor	^9.7.0 → ^12.0.9

---

Release Notes

SBoudrias/mem-fs (mem-fs-editor)

v12.0.9

Compare Source

Features

• Editor actions can now attach file metadata (#​88, closes #​67). All mutating actions (write, writeJSON, extendJSON, append, copy, copyAsync, copyTpl, copyTplAsync, move) accept an optional metadata object. It is attached to the mem-fs Vinyl file as editorMetadata and remains available during store.each, commit transforms and other downstream processing. Existing behavior is unchanged when no metadata is provided.
• The bare fs.Stats third argument of write() is deprecated in favor of the WriteOptions object form ({ stat }). Type overloads flag the deprecated form via typescript/no-deprecated.

Fixes

• Loosened the mem-fs peer dependency from ^4.0.0 to >=4.0.0 (#​95), so mem-fs v5 and v6 can be used with this release.

Notes

• Internal dependency bumps (dev dependencies only: lerna-lite, turbo, vitest, linting packages).
• No other public API or behavior changes.

v12.0.8

Compare Source

Fixes

• Restored 100% branch coverage after the lint migration by resolving type-aware Oxlint violations across src and tests.

Notes

Internal-only release — no public API or behavior changes. This release migrates the codebase from ESLint to type-aware Oxlint and applies the resulting refactors (explicit node: import prefixes, == null / != null presence checks, extracted copySingle helper, typed pipeline generics).

v12.0.7

Compare Source

Fixes

• Copying a single file to an exact destination when globOptions is set now works correctly again. Previously, passing globOptions forced a literal single-file copy()/copyAsync() through the glob branch, causing the source basename to be appended to the destination. This restores the pre-v8 behavior. (#​61)

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).

v12.0.6

Compare Source

• Fix: types dependencies were missing from dependencies leading to TS errors for users.

v12.0.5

Compare Source

mem-fs-editor 12.0.5

Fixes

• Fixed copy() so in-memory files matched during glob/directory copy respect fromBasePath, matching the existing copyAsync() behavior. Fixes #​63.
• Fixed copy() and copyAsync() to skip deleted in-memory files during directory/glob copies, preventing deleted entries from being copied or causing copy failures.

Package metadata

• Updated dependencies: ejs to ^6.0.1, minimatch to ^10.2.5.
• Published package now also exports ./package.json.
• Node engine metadata is now 20 || >=22.

v12.0.4

Compare Source

---

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 unable to resolve dependency tree
npm error
npm error While resolving: loopback-monorepo@undefined
npm error Found: mem-fs@2.3.0
npm error node_modules/mem-fs
npm error   dev mem-fs@"^2.3.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer mem-fs@">=4.0.0" from mem-fs-editor@12.0.9
npm error node_modules/mem-fs-editor
npm error   dev mem-fs-editor@"^12.0.9" from the root project
npm error   dev mem-fs-editor@"^12.0.9" from @loopback/cli@7.0.17
npm error   packages/cli
npm error     @loopback/cli@7.0.17
npm error     node_modules/@loopback/cli
npm error       workspace packages/cli from the root project
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_32_477Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-21T14_35_32_477Z-debug-0.log