Files
klz-cables.com/.pnpm-store/v10/files/34/e0a0670498380e68d47b3a85cfa87f8456eb1fc3027dfc54d08059d846ed113176908a86d6b28a0ac423477265cd659b400a7e284eb951efc7beea7f32c6f2
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

1 line
1.3 KiB
Plaintext

{"version":3,"sources":["../../src/__testing__/predefinedMigration.js"],"sourcesContent":["/**\n * Test predefined migration for testing plugin-style module specifier imports.\n * This is used in integration tests to verify that external packages (without @payloadcms/db-* prefix)\n * can export predefined migrations via their package.json exports.\n *\n * This tests the second code path in getPredefinedMigration.ts (lines 56-72)\n *\n * NOTE: This is a .js file (not .ts) because Node.js with --no-experimental-strip-types\n * cannot import .ts files via module specifiers. Absolute file paths work because Vitest's\n * loader intercepts file:// URLs, but module specifiers are resolved by Node.js first.\n */\nconst imports = ``\nconst upSQL = ` // Test predefined migration from payload/__testing__/predefinedMigration\n payload.logger.info('Test migration UP from payload package executed')`\nconst downSQL = ` // Test predefined migration DOWN from payload package\n payload.logger.info('Test migration DOWN from payload package executed')`\n\nexport { downSQL, imports, upSQL }\n"],"names":["imports","upSQL","downSQL"],"mappings":"AAAA;;;;;;;;;;CAUC,GACD,MAAMA,UAAU,EAAE;AAClB,MAAMC,QAAQ,CAAC;wEACyD,CAAC;AACzE,MAAMC,UAAU,CAAC;0EACyD,CAAC;AAE3E,SAASA,OAAO,EAAEF,OAAO,EAAEC,KAAK,GAAE"}