mocktomata@10.0.0

Major Changes

• 66fdf25: ESM only. The CommonJS build is removed.

  Every package now ships esm/ (lib/ for @mocktomata/cli) and nothing else. The cjs/
  directory, the cjs/package.json {"type":"commonjs"} marker and the main field are gone, and
  exports lists ESM entries only. mocktomata is a testing library, so its consumers are test
  suites, which have not needed require() for some time.

  What a require() of these packages does now depends on the Node version, and both outcomes were
  verified against the packed tarballs rather than assumed:

  • Node < 22.12 — require() throws ERR_REQUIRE_ESM with Node's own message pointing at
    import(). A clean, actionable failure.
  • Node >= 22.12 — Node's built-in require(esm) loads the package and returns the complete
    namespace. Every export is present and callable.

  The default condition still points at the ESM entry, so that second path keeps working. Dropping
  it would force a hard ERR_PACKAGE_PATH_NOT_EXPORTED on modern Node for no benefit; the module
  graph is genuinely ESM either way.

  Also in this release:

  • engines.node is now >= 20, the floor an ESM-only package can honestly claim.
  • @mocktomata/cli no longer depends on uni-require. It read its own package.json through a
    createRequire shim built from that package's import.meta.url, so the specifier resolved
    against uni-require's own directory and mt --version reported 1.0.0. It now resolves the
    manifest from import.meta.url and reports the CLI's version.
  • @mocktomata/framework declares standard-log-color as a dependency. Two of its modules import
    it, but it was listed under devDependencies, so the published package relied on a consumer
    happening to hoist it.
  • @mocktomata/service renames the internal jest module to test_server. It was never part of
    exports; @mocktomata/service/testing is unchanged.
  • @mocktomata/nodejs no longer publishes esm/testutils/fixture.js. It resolves ../../fixtures,
    a directory the tarball has never contained, and it is reachable from no exports path.

Minor Changes

• 98560f3: Depend on type-plus 8.0.0-beta.10 exactly, up from ^7.0.0.

  Minor, not major: type-plus is a runtime dependency here (ts/browser/context.ts uses
  requiredDeep and RequiredPick) but it does not leak into the published declarations — no
  emitted .d.ts in this package imports from type-plus, so consumers do not inherit
  type-plus@8's new typescript >= 5.6.0 peer through this package's own types. The last
  published mocktomata (9.2.3) declares type-plus: ^7.0.0, so that is the jump consumers see.

  The version is pinned exactly rather than caret-ranged. ^8.0.0-beta.10 resolves to
  >=8.0.0-beta.10 <9.0.0-0, which admits every later 8.0.0 prerelease plus 8.0.0 and
  8.1.0. type-plus 8 is a prerelease line where breaking changes land between betas —
  beta.10 to beta.11 changed Equal's signature and removed isType.f. An exact version makes
  each bump a reviewable pull request instead of something a lockfile refresh can do silently.
  This reverts to a caret once 8.0.0 is stable.

Patch Changes

• 98560f3: Raise the standard-log floor to ^13.1.0.

  standard-log@13.1.0 is the first 13.x on type-plus@8.0.0-beta.10; 13.0.1 still pulled
  type-plus@7.6.2. Raising the floor removes one of the duplicate type-plus majors from the
  installed tree. Range-compatible for consumers — ^13.0.1 already admitted 13.1.0.

• Updated dependencies [66fdf25]

• Updated dependencies [98560f3]

• Updated dependencies [98560f3]

• Updated dependencies [98560f3]

• Updated dependencies [98560f3]

  • @mocktomata/framework@10.0.0
  • @mocktomata/io-remote@10.0.0
  • @mocktomata/service@10.0.0
  • @mocktomata/nodejs@10.0.0

@mocktomata/service@10.0.0

Major Changes

• 66fdf25: ESM only. The CommonJS build is removed.

  Every package now ships esm/ (lib/ for @mocktomata/cli) and nothing else. The cjs/
  directory, the cjs/package.json {"type":"commonjs"} marker and the main field are gone, and
  exports lists ESM entries only. mocktomata is a testing library, so its consumers are test
  suites, which have not needed require() for some time.

  What a require() of these packages does now depends on the Node version, and both outcomes were
  verified against the packed tarballs rather than assumed:

  • Node < 22.12 — require() throws ERR_REQUIRE_ESM with Node's own message pointing at
    import(). A clean, actionable failure.
  • Node >= 22.12 — Node's built-in require(esm) loads the package and returns the complete
    namespace. Every export is present and callable.

  The default condition still points at the ESM entry, so that second path keeps working. Dropping
  it would force a hard ERR_PACKAGE_PATH_NOT_EXPORTED on modern Node for no benefit; the module
  graph is genuinely ESM either way.

  Also in this release:

  • engines.node is now >= 20, the floor an ESM-only package can honestly claim.
  • @mocktomata/cli no longer depends on uni-require. It read its own package.json through a
    createRequire shim built from that package's import.meta.url, so the specifier resolved
    against uni-require's own directory and mt --version reported 1.0.0. It now resolves the
    manifest from import.meta.url and reports the CLI's version.
  • @mocktomata/framework declares standard-log-color as a dependency. Two of its modules import
    it, but it was listed under devDependencies, so the published package relied on a consumer
    happening to hoist it.
  • @mocktomata/service renames the internal jest module to test_server. It was never part of
    exports; @mocktomata/service/testing is unchanged.
  • @mocktomata/nodejs no longer publishes esm/testutils/fixture.js. It resolves ../../fixtures,
    a directory the tarball has never contained, and it is reachable from no exports path.

Minor Changes

• 98560f3: Depend on type-plus 8.0.0-beta.10 exactly, up from ^7.0.0.

  Minor, not major: type-plus is a runtime dependency here (ts/test_server.ts uses
  required) but it does not leak into the published declarations — no emitted .d.ts in this
  package imports from type-plus, so consumers do not inherit type-plus@8's new
  typescript >= 5.6.0 peer through this package's own types. The last published
  @mocktomata/service (9.2.4) declares type-plus: ^7.0.0, so that is the jump consumers see.

  The version is pinned exactly rather than caret-ranged. ^8.0.0-beta.10 resolves to
  >=8.0.0-beta.10 <9.0.0-0, which admits every later 8.0.0 prerelease plus 8.0.0 and
  8.1.0. type-plus 8 is a prerelease line where breaking changes land between betas —
  beta.10 to beta.11 changed Equal's signature and removed isType.f. An exact version makes
  each bump a reviewable pull request instead of something a lockfile refresh can do silently.
  This reverts to a caret once 8.0.0 is stable.

Patch Changes

• 98560f3: Raise the standard-log floor to ^13.1.0.

  standard-log@13.1.0 is the first 13.x on type-plus@8.0.0-beta.10; 13.0.1 still pulled
  type-plus@7.6.2. Raising the floor removes one of the duplicate type-plus majors from the
  installed tree. Range-compatible for consumers — ^13.0.1 already admitted 13.1.0.

• Updated dependencies [66fdf25]

• Updated dependencies [98560f3]

• Updated dependencies [98560f3]

• Updated dependencies [98560f3]

  • @mocktomata/framework@10.0.0
  • @mocktomata/nodejs@10.0.0

@mocktomata/plugin-axios@3.0.0

Major Changes

• 66fdf25: ESM only. The CommonJS build is removed.

  Every package now ships esm/ (lib/ for @mocktomata/cli) and nothing else. The cjs/
  directory, the cjs/package.json {"type":"commonjs"} marker and the main field are gone, and
  exports lists ESM entries only. mocktomata is a testing library, so its consumers are test
  suites, which have not needed require() for some time.

  What a require() of these packages does now depends on the Node version, and both outcomes were
  verified against the packed tarballs rather than assumed:

  • Node < 22.12 — require() throws ERR_REQUIRE_ESM with Node's own message pointing at
    import(). A clean, actionable failure.
  • Node >= 22.12 — Node's built-in require(esm) loads the package and returns the complete
    namespace. Every export is present and callable.

  The default condition still points at the ESM entry, so that second path keeps working. Dropping
  it would force a hard ERR_PACKAGE_PATH_NOT_EXPORTED on modern Node for no benefit; the module
  graph is genuinely ESM either way.

  Also in this release:

  • engines.node is now >= 20, the floor an ESM-only package can honestly claim.
  • @mocktomata/cli no longer depends on uni-require. It read its own package.json through a
    createRequire shim built from that package's import.meta.url, so the specifier resolved
    against uni-require's own directory and mt --version reported 1.0.0. It now resolves the
    manifest from import.meta.url and reports the CLI's version.
  • @mocktomata/framework declares standard-log-color as a dependency. Two of its modules import
    it, but it was listed under devDependencies, so the published package relied on a consumer
    happening to hoist it.
  • @mocktomata/service renames the internal jest module to test_server. It was never part of
    exports; @mocktomata/service/testing is unchanged.
  • @mocktomata/nodejs no longer publishes esm/testutils/fixture.js. It resolves ../../fixtures,
    a directory the tarball has never contained, and it is reachable from no exports path.

Patch Changes

• Updated dependencies [66fdf25]
• Updated dependencies [98560f3]
• Updated dependencies [98560f3]
  • mocktomata@10.0.0

@mocktomata/nodejs@10.0.0

Major Changes

• 66fdf25: ESM only. The CommonJS build is removed.

  Every package now ships esm/ (lib/ for @mocktomata/cli) and nothing else. The cjs/
  directory, the cjs/package.json {"type":"commonjs"} marker and the main field are gone, and
  exports lists ESM entries only. mocktomata is a testing library, so its consumers are test
  suites, which have not needed require() for some time.

  What a require() of these packages does now depends on the Node version, and both outcomes were
  verified against the packed tarballs rather than assumed:

  • Node < 22.12 — require() throws ERR_REQUIRE_ESM with Node's own message pointing at
    import(). A clean, actionable failure.
  • Node >= 22.12 — Node's built-in require(esm) loads the package and returns the complete
    namespace. Every export is present and callable.

  The default condition still points at the ESM entry, so that second path keeps working. Dropping
  it would force a hard ERR_PACKAGE_PATH_NOT_EXPORTED on modern Node for no benefit; the module
  graph is genuinely ESM either way.

  Also in this release:

  • engines.node is now >= 20, the floor an ESM-only package can honestly claim.
  • @mocktomata/cli no longer depends on uni-require. It read its own package.json through a
    createRequire shim built from that package's import.meta.url, so the specifier resolved
    against uni-require's own directory and mt --version reported 1.0.0. It now resolves the
    manifest from import.meta.url and reports the CLI's version.
  • @mocktomata/framework declares standard-log-color as a dependency. Two of its modules import
    it, but it was listed under devDependencies, so the published package relied on a consumer
    happening to hoist it.
  • @mocktomata/service renames the internal jest module to test_server. It was never part of
    exports; @mocktomata/service/testing is unchanged.
  • @mocktomata/nodejs no longer publishes esm/testutils/fixture.js. It resolves ../../fixtures,
    a directory the tarball has never contained, and it is reachable from no exports path.

Minor Changes

• 98560f3: Depend on type-plus 8.0.0-beta.10 exactly, up from ^7.0.0.

  Minor, not major: type-plus is a runtime dependency here (ts/io.ts uses reduceByKey)
  but it does not leak into the published declarations — no emitted .d.ts in this package
  imports from type-plus, so consumers do not inherit type-plus@8's new
  typescript >= 5.6.0 peer through this package's own types. The last published
  @mocktomata/nodejs (9.2.4) declares type-plus: ^7.0.0, so that is the jump consumers see.

  The version is pinned exactly rather than caret-ranged. ^8.0.0-beta.10 resolves to
  >=8.0.0-beta.10 <9.0.0-0, which admits every later 8.0.0 prerelease plus 8.0.0 and
  8.1.0. type-plus 8 is a prerelease line where breaking changes land between betas —
  beta.10 to beta.11 changed Equal's signature and removed isType.f. An exact version makes
  each bump a reviewable pull request instead of something a lockfile refresh can do silently.
  This reverts to a caret once 8.0.0 is stable.

Patch Changes

• 98560f3: Raise the standard-log floor to ^13.1.0.

  standard-log@13.1.0 is the first 13.x on type-plus@8.0.0-beta.10; 13.0.1 still pulled
  type-plus@7.6.2. Raising the floor removes one of the duplicate type-plus majors from the
  installed tree. Range-compatible for consumers — ^13.0.1 already admitted 13.1.0.

• Updated dependencies [66fdf25]

• Updated dependencies [98560f3]

• Updated dependencies [98560f3]

  • @mocktomata/framework@10.0.0

@mocktomata/io-remote@10.0.0

Major Changes

• 66fdf25: ESM only. The CommonJS build is removed.

  Every package now ships esm/ (lib/ for @mocktomata/cli) and nothing else. The cjs/
  directory, the cjs/package.json {"type":"commonjs"} marker and the main field are gone, and
  exports lists ESM entries only. mocktomata is a testing library, so its consumers are test
  suites, which have not needed require() for some time.

  What a require() of these packages does now depends on the Node version, and both outcomes were
  verified against the packed tarballs rather than assumed:

  • Node < 22.12 — require() throws ERR_REQUIRE_ESM with Node's own message pointing at
    import(). A clean, actionable failure.
  • Node >= 22.12 — Node's built-in require(esm) loads the package and returns the complete
    namespace. Every export is present and callable.

  The default condition still points at the ESM entry, so that second path keeps working. Dropping
  it would force a hard ERR_PACKAGE_PATH_NOT_EXPORTED on modern Node for no benefit; the module
  graph is genuinely ESM either way.

  Also in this release:

  • engines.node is now >= 20, the floor an ESM-only package can honestly claim.
  • @mocktomata/cli no longer depends on uni-require. It read its own package.json through a
    createRequire shim built from that package's import.meta.url, so the specifier resolved
    against uni-require's own directory and mt --version reported 1.0.0. It now resolves the
    manifest from import.meta.url and reports the CLI's version.
  • @mocktomata/framework declares standard-log-color as a dependency. Two of its modules import
    it, but it was listed under devDependencies, so the published package relied on a consumer
    happening to hoist it.
  • @mocktomata/service renames the internal jest module to test_server. It was never part of
    exports; @mocktomata/service/testing is unchanged.
  • @mocktomata/nodejs no longer publishes esm/testutils/fixture.js. It resolves ../../fixtures,
    a directory the tarball has never contained, and it is reachable from no exports path.

Patch Changes

• 98560f3: Raise the standard-log floor to ^13.1.0.

  standard-log@13.1.0 is the first 13.x on type-plus@8.0.0-beta.10; 13.0.1 still pulled
  type-plus@7.6.2. Raising the floor removes one of the duplicate type-plus majors from the
  installed tree. Range-compatible for consumers — ^13.0.1 already admitted 13.1.0.

• Updated dependencies [66fdf25]

• Updated dependencies [98560f3]

• Updated dependencies [98560f3]

  • @mocktomata/framework@10.0.0

@mocktomata/framework@10.0.0

Major Changes

• 66fdf25: ESM only. The CommonJS build is removed.

  Every package now ships esm/ (lib/ for @mocktomata/cli) and nothing else. The cjs/
  directory, the cjs/package.json {"type":"commonjs"} marker and the main field are gone, and
  exports lists ESM entries only. mocktomata is a testing library, so its consumers are test
  suites, which have not needed require() for some time.

  What a require() of these packages does now depends on the Node version, and both outcomes were
  verified against the packed tarballs rather than assumed:

  • Node < 22.12 — require() throws ERR_REQUIRE_ESM with Node's own message pointing at
    import(). A clean, actionable failure.
  • Node >= 22.12 — Node's built-in require(esm) loads the package and returns the complete
    namespace. Every export is present and callable.

  The default condition still points at the ESM entry, so that second path keeps working. Dropping
  it would force a hard ERR_PACKAGE_PATH_NOT_EXPORTED on modern Node for no benefit; the module
  graph is genuinely ESM either way.

  Also in this release:

  • engines.node is now >= 20, the floor an ESM-only package can honestly claim.
  • @mocktomata/cli no longer depends on uni-require. It read its own package.json through a
    createRequire shim built from that package's import.meta.url, so the specifier resolved
    against uni-require's own directory and mt --version reported 1.0.0. It now resolves the
    manifest from import.meta.url and reports the CLI's version.
  • @mocktomata/framework declares standard-log-color as a dependency. Two of its modules import
    it, but it was listed under devDependencies, so the published package relied on a consumer
    happening to hoist it.
  • @mocktomata/service renames the internal jest module to test_server. It was never part of
    exports; @mocktomata/service/testing is unchanged.
  • @mocktomata/nodejs no longer publishes esm/testutils/fixture.js. It resolves ../../fixtures,
    a directory the tarball has never contained, and it is reachable from no exports path.

• 98560f3: Depend on type-plus 8.0.0-beta.10 exactly, up from ^7.0.0.

  This is a major for this package because type-plus types leak into the published
  declarations: esm/**/*.d.ts imports AnyFunction, AnyRecord, JSONTypes and
  RequiredPick from type-plus. type-plus@8 declares
  peerDependencies: { typescript: '>= 5.6.0' } where 5, 6 and 7 declared no TypeScript peer at
  all, so consumers of @mocktomata/framework inherit a TypeScript floor they did not have
  before. The last published @mocktomata/framework (9.2.4) declares type-plus: ^7.0.0, so
  that is the jump consumers actually see.

  type-plus@8 also brings unpartial@^1.0.7, whose engines require Node >= 20. This
  package already declares >= 20, so nothing changes there.

  The version is pinned exactly rather than caret-ranged. ^8.0.0-beta.10 resolves to
  >=8.0.0-beta.10 <9.0.0-0, which admits every later 8.0.0 prerelease plus 8.0.0 and
  8.1.0. type-plus 8 is a prerelease line where breaking changes land between betas —
  beta.10 to beta.11 changed Equal's signature and removed isType.f. An exact version makes
  each bump a reviewable pull request instead of something a lockfile refresh can do silently.
  This reverts to a caret once 8.0.0 is stable.

Patch Changes

• 98560f3: Raise the standard-log floor to ^13.1.0.

  standard-log@13.1.0 is the first 13.x on type-plus@8.0.0-beta.10; 13.0.1 still pulled
  type-plus@7.6.2. Raising the floor removes one of the duplicate type-plus majors from the
  installed tree. Range-compatible for consumers — ^13.0.1 already admitted 13.1.0.

@mocktomata/cli@10.0.0

Major Changes

• 66fdf25: ESM only. The CommonJS build is removed.

  Every package now ships esm/ (lib/ for @mocktomata/cli) and nothing else. The cjs/
  directory, the cjs/package.json {"type":"commonjs"} marker and the main field are gone, and
  exports lists ESM entries only. mocktomata is a testing library, so its consumers are test
  suites, which have not needed require() for some time.

  What a require() of these packages does now depends on the Node version, and both outcomes were
  verified against the packed tarballs rather than assumed:

  • Node < 22.12 — require() throws ERR_REQUIRE_ESM with Node's own message pointing at
    import(). A clean, actionable failure.
  • Node >= 22.12 — Node's built-in require(esm) loads the package and returns the complete
    namespace. Every export is present and callable.

  The default condition still points at the ESM entry, so that second path keeps working. Dropping
  it would force a hard ERR_PACKAGE_PATH_NOT_EXPORTED on modern Node for no benefit; the module
  graph is genuinely ESM either way.

  Also in this release:

  • engines.node is now >= 20, the floor an ESM-only package can honestly claim.
  • @mocktomata/cli no longer depends on uni-require. It read its own package.json through a
    createRequire shim built from that package's import.meta.url, so the specifier resolved
    against uni-require's own directory and mt --version reported 1.0.0. It now resolves the
    manifest from import.meta.url and reports the CLI's version.
  • @mocktomata/framework declares standard-log-color as a dependency. Two of its modules import
    it, but it was listed under devDependencies, so the published package relied on a consumer
    happening to hoist it.
  • @mocktomata/service renames the internal jest module to test_server. It was never part of
    exports; @mocktomata/service/testing is unchanged.
  • @mocktomata/nodejs no longer publishes esm/testutils/fixture.js. It resolves ../../fixtures,
    a directory the tarball has never contained, and it is reachable from no exports path.

Patch Changes

• Updated dependencies [66fdf25]
• Updated dependencies [98560f3]
• Updated dependencies [98560f3]
  • @mocktomata/service@10.0.0

@mocktomata/service@9.2.4

Patch Changes

• 0f3de8f: Pick up the republished upstream packages.

  Runtime dependency ranges move to standard-log@^13.0.1 and tersify@^4.0.6. Both
  majors are build-target and packaging changes rather than API changes — standard-log 13
  is a tsdown rebuild whose only removals are unreferenced dist/ bundles, and tersify 4
  retargets ES2020 and renames its outputs to .cjs/.mjs. Every symbol this repo
  imports is still exported, both still ship a CommonJS entry point, and neither declares
  an engines floor. This is a patch: what ships is rebuilt, no public API changes.

  standard-log-color deliberately stays on ^12.1.2. Version 13.0.1 raises
  supports-color to ^11.0.0, which is ESM-only and requires Node >= 22, while
  standard-log-color still publishes a CommonJS build that require()s it — so its CJS
  consumers break in browser and Electron environments.

• Updated dependencies [0f3de8f]

  • @mocktomata/framework@9.2.4
  • @mocktomata/nodejs@9.2.4

@mocktomata/plugin-axios@2.0.4

@mocktomata/plugin-axios@2.0.4

@mocktomata/nodejs@9.2.4

Patch Changes

• 0f3de8f: Pick up the republished upstream packages.

  Runtime dependency ranges move to standard-log@^13.0.1 and tersify@^4.0.6. Both
  majors are build-target and packaging changes rather than API changes — standard-log 13
  is a tsdown rebuild whose only removals are unreferenced dist/ bundles, and tersify 4
  retargets ES2020 and renames its outputs to .cjs/.mjs. Every symbol this repo
  imports is still exported, both still ship a CommonJS entry point, and neither declares
  an engines floor. This is a patch: what ships is rebuilt, no public API changes.

  standard-log-color deliberately stays on ^12.1.2. Version 13.0.1 raises
  supports-color to ^11.0.0, which is ESM-only and requires Node >= 22, while
  standard-log-color still publishes a CommonJS build that require()s it — so its CJS
  consumers break in browser and Electron environments.

• Updated dependencies [0f3de8f]

  • @mocktomata/framework@9.2.4