Lukas Koeller

Results 15 comments of Lukas Koeller

Might be worth adding that I used `Assume Role directly using GitHub OIDC provider` (see [Configure AWS Credentials for GitHub Actions](https://github.com/marketplace/actions/configure-aws-credentials-for-github-actions#assuming-a-role)) to setup credentials

# Workaround Solution The main problem here is the `@vitejs/plugin-legacy` in the `vite.config.ts`. If you comment the import and its usage out or remove it, the command works fine.

@KusStar I had the same issue using `npx`. The path to the vite app I tested `my-monorepo/src/mf/my-app/vite.config.ts` Excerpt of the error pointing to the vite legacy plugin: ```shell code: 'PLUGIN_ERROR',...

Dependencies from `package.json`: ```json "dependencies": { "@companyName/api": "workspace:*", "@companyName/assets": "workspace:*", "@companyName/components": "workspace:*", "@companyName/data": "workspace:*", "@companyName/data-deprecated": "workspace:*", "@companyName/error": "workspace:*", "@companyName/project-configs": "workspace:*", "@companyName/theme": "workspace:*", "@companyName/types": "workspace:*", "@companyName/utils": "workspace:*", "@companyName/validate": "workspace:*", "dayjs": "^1.11.5",...

> Your project structure is complex. Can you provide a reproduce repo? Sure. Here is a repro on Stackblitz: https://stackblitz.com/edit/vitejs-vite-mkjnwn?file=vite.config.ts I literally just added the [`@vitejs/plugin-legacy`](https://github.com/vitejs/vite/tree/main/packages/plugin-legacy) package and adjusted `vite.config.ts`...