`taze.config.js` no longer working since v0.13.9

NimmLor commented 2 months ago

Describe the bug

Since v0.13.9 (also v0.14.0) taze does no longer pick up my config file. Downgrading to v0.13.8 resolves this issue. I'm running it in a monorepo using yarn workspaces.

UPDATE: Seems to be caused by the bump of unconfig to v0.4, adding the resolution fixed it for me:

  "resolutions": {
    "unconfig": "0.3.13"
  }

package.json

{
  "name": "root",
  "workspaces": [
    "apps/*",
    "packages/*",
    "backend",
    "infra"
  ],
  "scripts": {
    "deps:upgrade": "taze -w",
  },
  "devDependencies": {
    "taze": "0.13.9"
  },
  "packageManager": "yarn@4.3.1"
}

taze.config.js

import { defineConfig } from 'taze'

export default defineConfig({
  exclude: ['@aws-sdk/*', '@types/node'],
  install: false,
  packageMode: {
    typescript: 'major',
  },
  recursive: true,
})

Reproduction

install v0.13.9 or 0.14.0

System Info

System:
  OS: Windows 11 10.0.22631
  CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700K
  Memory: 15.03 GB / 31.75 GB
Binaries:
  Node: 20.14.0 - C:\Program Files\nodejs\node.EXE
  Yarn: 4.3.1 - ~\AppData\Roaming\npm\yarn.CMD
  npm: 10.7.0 - C:\Program Files\nodejs\npm.CMD
  pnpm: 7.26.3 - ~\AppData\Local\pnpm\pnpm.EXE
  bun: 1.1.8 - ~\.bun\bin\bun.EXE
Browsers:
  Edge: Chromium (126.0.2592.81)
  Internet Explorer: 11.0.22621.3527

Same issue in Linux GitHub Actions Runner using node v20.12.1

Used Package Manager

yarn

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.