v6.0.1

Patch Changes

• 0bec60d: Move the TypeScript sources from ts/ to src/.

  The published package now ships its sources under src/, and the emitted
  declaration and source maps resolve against that path. The public entry points
  (esm/index.js, esm/index.d.ts) are unchanged.

v6.0.0

Major Changes

• fa8b087: Adopt the current majors of the first-party dependencies: standard-log
^11.5.2 -> ^13.2.0, standard-log-color ^12.0.0 -> ^13.2.0, tersify
^3.12.1 -> ^4.0.7, and iso-error ^6.0.5 -> ^7.0.0.

  Why this matters to consumers. Installing @unional/fixture@5.0.0 resolved
  five majors of type-plus and two of tersify. The old standard-log@11 line
  pulls @just-func/types@0.5.1, which still depends on type-plus@^5.0.0, so
  type-plus@5.6.0 and type-plus@6.8.1 were nested under this package in every
  consumer's tree, and tersify@3.12.1 was hoisted out of it. This release
  removes all three: type-plus and tersify each resolve to a single version
  (8.0.0-beta.10 and 4.0.7), and standard-log to 13.2.0 only.

  Breaking. Logger (standard-log), IsoError (iso-error) and
  Tersible (tersify) all appear in this package's emitted .d.ts, so a
  consumer's own copies of those packages must move with it. standard-log@13
  also drops ES5 output.

  engines.node is unchanged at >= 20; iso-error@7.0.0's major was that same
  raise, which this package had already made.

  No behaviour of @unional/fixture changes. The only source change is in a
  test: createStandardLogForTest() moved to the standard-log/testing subpath
  in standard-log@12. tersify@4 preserves the source's own quote style rather
  than normalising to double quotes, but no assertion in this package's suite
  embeds tersified function source, so no expectation moved.

v5.0.0

Major Changes

• 56090b6: Pin type-plus to the exact version 8.0.0-beta.10.

  type-plus 8 is still a prerelease line where breaking changes have landed between
  betas (for example beta.10 changed Equal's signature and removed isType.f), so
  type-plus is pinned to an exact version rather than a caret range: ^8.0.0-beta.10
  would admit every later 8.0.0 prerelease plus 8.0.0 and 8.1.0, letting a lockfile
  refresh silently pull in a breaking prerelease. An exact pin makes each bump a
  reviewable PR instead.

  type-plus types are re-exported through this package's public API (PartialPick
  in command.d.ts), so consumers now inherit type-plus@8's typescript >= 5.6.0
  peer dependency requirement.

  Also raises the minimum supported Node.js version from >= 18 to >= 20, matching
  the floor required by type-plus@8's unpartial dependency (engines: { node: '>= 20' }). This is independently breaking for consumers still on Node 18 or 19.

  Migration:

  • Ensure your project uses TypeScript >= 5.6.0.
  • Ensure your project runs on Node.js >= 20.

  This release lets clibuilder, repobuddy and mocktomata drop a stale transitive
  type-plus that this package was keeping alive.

v4.0.0

Major Changes

• b1f2eab: Drop CommonJS support. The package is now ESM-only.

  There is no cjs/ output any more and exports resolves only to
  ./esm/index.js. Import it:

  import { baseline } from '@unional/fixture'

  What this breaks, precisely:

  • require('@unional/fixture') from a CommonJS file on Node older than 22.12
    now throws ERR_REQUIRE_ESM. Move the calling test file to ESM, or use
    const { baseline } = await import('@unional/fixture').
  • On Node 22.12 and newer, require() of an ES module is supported by Node
    itself and keeps working against the ESM entry.

  engines.node is now declared as >= 18 — the floor the dependencies already
  required, previously left unstated.

  Node builtins are now imported with the node: prefix (node:fs, node:path,
  node:os), which is what the published esm/ output carries. Bare fs does not
  resolve under Deno; node:fs resolves under Node, Deno and Bun alike, so the
  package is importable from more runtimes than before.

  Nothing the ESM entry exports changed: same names, same types, same esm/
  paths as 3.2.x.

Patch Changes

• 4e085ac: Drop the mkdirp dependency in favour of fs.mkdirSync(path, { recursive: true }).

  ensureFolderExist() behaves identically — mkdirp.sync has been a wrapper over
  Node's own recursive mkdir since Node 10. Removing it also removes the stale
  @types/mkdirp (v1 types against a v2 runtime) and retires the renovate PR that
  could not pass: mkdirp v3 dropped the default export, so import mkdirp from 'mkdirp'
  fails outright.

v3.2.18

Patch Changes

• 476100c: Point repository, homepage and bugs at cyberuni/fixture.

  repository is read when generating provenance attestations, so it has to be correct at
  publish time — not merely correct in the repo.

v3.2.17

3.2.17 (2023-05-30)

Bug Fixes

• deps: update dependency type-plus to v7 (#205) (c9e6148)

v3.2.16

3.2.16 (2023-04-13)

Bug Fixes

• deps: update dependency standard-log-color to v12 (#201) (a209e91)

v3.2.15

3.2.15 (2023-04-02)

Bug Fixes

• deps: update dependency minimatch to v8 (#194) (794e5de)

v3.2.14

3.2.14 (2023-03-17)

Bug Fixes

• deps: update dependency type-plus to v6 (#192) (765667a)

v3.2.13

3.2.13 (2023-02-20)

Bug Fixes

• deps: update dependency minimatch to v7 (#187) (839dfcf)