Files
klz-cables.com/.pnpm-store/v10/files/ca/9cfa0186d0cadd56171e6c0af102ce0f6c02d092106b6d34798f9b69e77eb2192c4e896d913d5b7ecb01bee2012c0f74f0e3239c49f53eac277303270ab376
Marc Mintel 5397309103
Some checks failed
Build & Deploy / 🔍 Prepare (push) Successful in 20s
Build & Deploy / 🧪 QA (push) Failing after 34s
Build & Deploy / 🏗️ Build (push) Has started running
Build & Deploy / 🚀 Deploy (push) Has been cancelled
Build & Deploy / 🧪 Smoke Test (push) Has been cancelled
Build & Deploy / ⚡ Lighthouse (push) Has been cancelled
Build & Deploy / 🔔 Notify (push) Has been cancelled
fix(products): fix breadcrumbs and product filtering (backport from main)
2026-02-24 16:04:21 +01:00

18 lines
1.0 KiB
Plaintext

/**
* Test predefined migration for testing plugin-style module specifier imports.
* This is used in integration tests to verify that external packages (without @payloadcms/db-* prefix)
* can export predefined migrations via their package.json exports.
*
* This tests the second code path in getPredefinedMigration.ts (lines 56-72)
*
* NOTE: This is a .js file (not .ts) because Node.js with --no-experimental-strip-types
* cannot import .ts files via module specifiers. Absolute file paths work because Vitest's
* loader intercepts file:// URLs, but module specifiers are resolved by Node.js first.
*/ const imports = ``;
const upSQL = ` // Test predefined migration from payload/__testing__/predefinedMigration
payload.logger.info('Test migration UP from payload package executed')`;
const downSQL = ` // Test predefined migration DOWN from payload package
payload.logger.info('Test migration DOWN from payload package executed')`;
export { downSQL, imports, upSQL };
//# sourceMappingURL=predefinedMigration.js.map