expect(received).not.toThrow() Error name: "Error" Error message: "Command failed: npm run --workspace test-app build STDERR: - Building...· ✘ [ERROR] Could not resolve \"@o3r/rules-engine\" node_modules/@o3r/components/fesm2022/o3r-components.mjs:476:65: 476 │ ...= from(import( /* @vite-ignore */`${'@o3r/rules-engine'}`)).pipe( ╵ ^ You can mark the path \"@o3r/rules-engine\" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also add \".catch()\" here to handle this failure at run-time instead of bundle-time. ✘ [ERROR] Could not resolve \"@o3r/dynamic-content\" node_modules/@o3r/components/fesm2022/o3r-components.mjs:565:68: 565 │ ...from(import( /* @vite-ignore */`${'@o3r/dynamic-content'}`)).p... ╵ ^ You can mark the path \"@o3r/dynamic-content\" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also add \".catch()\" here to handle this failure at run-time instead of bundle-time. ✘ [ERROR] Could not resolve \"@o3r/localization\" node_modules/@o3r/components/fesm2022/o3r-components.mjs:604:68: 604 │ ...h(from(import( /* @vite-ignore */`${'@o3r/localization'}`)).pipe( ╵ ^ You can mark the path \"@o3r/localization\" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also add \".catch()\" here to handle this failure at run-time instead of bundle-time. npm ERR! Lifecycle script `build` failed with error:· npm ERR! Error: command failed· npm ERR! in workspace: [email protected]· npm ERR! at location: /home/runner/work/otter/it-tests/test-app-components/apps/test-app·· OUTPUT: , > [email protected] build > ng build· Application bundle generation failed. [5.546 seconds]· ,- Building...· ✘ [ERROR] Could not resolve \"@o3r/rules-engine\" node_modules/@o3r/components/fesm2022/o3r-components.mjs:476:65: 476 │ ...= from(import( /* @vite-ignore */`${'@o3r/rules-engine'}`)).pipe( ╵ ^ You can mark the path \"@o3r/rules-engine\" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also add \".catch()\" here to handle this failure at run-time instead of bundle-time. ✘ [ERROR] Could not resolve \"@o3r/dynamic-content\" node_modules/@o3r/components/fesm2022/o3r-components.mjs:565:68: 565 │ ...from(import( /* @vite-ignore */`${'@o3r/dynamic-content'}`)).p... ╵ ^ You can mark the path \"@o3r/dynamic-content\" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also add \".catch()\" here to handle this failure at run-time instead of bundle-time. ✘ [ERROR] Could not resolve \"@o3r/localization\" node_modules/@o3r/components/fesm2022/o3r-components.mjs:604:68: 604 │ ...h(from(import( /* @vite-ignore */`${'@o3r/localization'}`)).pipe( ╵ ^ You can mark the path \"@o3r/localization\" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also add \".catch()\" here to handle this failure at run-time instead of bundle-time. npm ERR! Lifecycle script `build` failed with error:· npm ERR! Error: command failed· npm ERR! in workspace: [email protected]· npm ERR! at location: /home/runner/work/otter/it-tests/test-app-components/apps/test-app· " 81 | // Yarn doesn't log errors on stderr, so we need to get them from stdout to have them in the reports 82 | // eslint-disable-next-line @typescript-eslint/restrict-template-expressions > 83 | throw new Error(`Command failed: ${args.join(' ') }\nSTDERR:

Process completed with exit code 1.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/upload-artifact@a8a3f3ad30e3422c9c7b888a15615d19a852ae32. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.