You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Writing asynchronously in defineConfig will cause npm run build to fail when Github Action executes the job of docker/build-push-action@v5, but local packaging is completely normal.
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
You are not calling resolve or reject when !!err is true. Not calling either of them causes Node.js to exit the process without any messages (nodejs/promises-debugging#16).
You are not calling resolve or reject when !!err is true. Not calling either of them causes Node.js to exit the process without any messages (nodejs/promises-debugging#16).
Describe the bug
Writing asynchronously in defineConfig will cause npm run build to fail when Github Action executes the job of docker/build-push-action@v5, but local packaging is completely normal.
Reproduction
https://github.com/zyronon/docker-test
Steps to reproduce
Https://github.com/zyronon/docker-test/, which is a new project just created with pnpm create vite, in which only the vite.config.ts file is modified
It is found that this method of writing is normal for local packaging, but it will fail in Github Action and do not report an error.
However, there is no problem with this writing either locally or in
Github Action
.System Info
Used Package Manager
pnpm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: