chore: update dependency mem-fs-editor to v12

[renovate]

This PR contains the following updates:

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

---

Release Notes

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

v12.0.3

Compare Source

• fix: add compatibility support (#​374) ae7bb78
• fix: do not remove .ejs extension if the output is expected to be an ejs file (#​368) 3cf8f1d
• feat: change parameters of fileTransform to object (#​360) 9f07207

---

v12.0.2

Compare Source

• fix: move @​types/picomatch to dependencies 688f726

---

v12.0.1

Compare Source

• fix: disable skipLibCheck in tsconfig.build.json (#​367) 2f25017
• chore: enable noImplicitAny in tsconfig.build.json (#​366) fde9f54

---

v12.0.0

Compare Source

🚀 mem-fs-editor v12 – Release Notes

🔄 Major Internal Rewrite

The internal implementation of mem-fs-editor has been almost completely rewritten.

What this means:

• Cleaner and more maintainable internal architecture
• Improved consistency across core operations
• Better separation of concerns
• Stronger foundation for future enhancements
• Reduced technical debt

🔧 templateOptions Refactoring

The templateOptions parameter, previously the 4th argument of methods such as copyTpl, has been moved inside the options object (the 4th and only options parameter).

Before:

copyTpl(
  'file.js.ejs',
  'file.js',
  data,
  { delimiter: '?' },
  { someOption: true }
);

After:

copyTpl(
  'file.js.ejs',
  'file.js',
  data,
  {
    someOption: true,
    transformOptions: { delimiter: '?' }
  }
);

🎯 Why This Change?

• templateOptions is not commonly used
• Improves API clarity and readability
• Reduces ambiguity around parameter ordering

v11.1.4

Compare Source

What's Changed

• fix: replace Duplex with Transform by @​mshima in #​282

Full Changelog: SBoudrias/mem-fs-editor@v11.1.3...v11.1.4

v11.1.3

Compare Source

• chore: update isbinaryfile and accept newer versions (#​280) ed06a83

v11.1.2

Compare Source

• have a permissive @​types/node version (#​279) b36dacf

v11.1.1

Compare Source

• fix isVinyl import ed832f0

v11.1.0

Compare Source

• normalize path for multimatch. (#​259) 7685ac8
• keep file history (#​249) 22ce794
• update dependencies

v11.0.1

Compare Source

• fix fromBasePath option (#​246) 1496cdf
• isbinaryfile does not follow semver for supported node, use fixed version (#​241) a55415b

v11.0.0

Compare Source

Breaking: Commit now uses mem-fs pipeline which recreate mem-fs files based on emitted files.

• use pipeline from mem-fs@​4 (#​229) e5f563a
• Update README.md (#​221) 5518e6c
• fix: add missing node type. (#​220) ee2d022

v10.0.3

Compare Source

• accept mem-fs@​4 478c841

v10.0.2

Compare Source

• fix: dump with filter regression (#​218) 2e7a021
• fix: bump node to v16 (#​219) ba9f1ec

v10.0.1

Compare Source

• Publish fixes (#​217) b32fd69

v10.0.0

Compare Source

The mem-fs-editor package now export a native ESM module. (Learn more about ESM)

---

Configuration

📅 Schedule: 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 this update 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 stop working in the next 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/cli@7.0.12
npm error Found: mem-fs@2.3.0
npm error node_modules/mem-fs
npm error   dev mem-fs@"^2.3.0" from @loopback/cli@7.0.12
npm error   packages/cli
npm error     @loopback/cli@7.0.12
npm error     node_modules/@loopback/cli
npm error       workspace packages/cli 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.3
npm error node_modules/mem-fs-editor
npm error   dev mem-fs-editor@"^12.0.3" from @loopback/cli@7.0.12
npm error   packages/cli
npm error     @loopback/cli@7.0.12
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-03-21T04_43_05_627Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-21T04_43_05_627Z-debug-0.log