From cc786aac4e9529d41142b1d89c2966077b4d8e5b Mon Sep 17 00:00:00 2001 From: Joseph Mearman Date: Thu, 17 Sep 2026 16:35:20 +0100 Subject: [PATCH] fix(build): scope prepublishOnly's attw check to the node16 profile attw --pack defaults to its own "strict" profile, which includes node10 (pre-exports-field) resolution, whereas tsdown's own build-time attw check already targets node16 explicitly. A single "." export happened to satisfy node10 resolution too, masking the mismatch, but a genuine multi-entry subpath export (cc-peer/alias-pool) cannot be resolved under node10 by design: legacy resolution has no concept of package exports beyond "main"/"types". Passing --profile node16 aligns the standalone prepublish check with the compatibility target this package already states everywhere else. --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 4047135..971ae69 100644 --- a/package.json +++ b/package.json @@ -69,7 +69,7 @@ "test:integration": "vitest run --project integration", "test:e2e": "vitest run --config vitest.e2e.config.ts", "test:mutation": "stryker run stryker.config.ts", - "prepublishOnly": "pnpm lint && pnpm typecheck && pnpm test:coverage && pnpm build && publint && attw --pack", + "prepublishOnly": "pnpm lint && pnpm typecheck && pnpm test:coverage && pnpm build && publint && attw --pack --profile node16", "prepare": "husky", "test:coverage": "vitest run --coverage" },