-
-
Notifications
You must be signed in to change notification settings - Fork 352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error thrown while building app in Github Actions #1450
Comments
This is likely a duplicate of a previous issue that was already fixed. Update to the latest version; I'll re-open if you still get this. |
Thank you for the ultra-quick response. I just tried re-running with the latest version of Vike and got what looks to be the same error:
|
I'm afraid I'll need a reproduction for this. Is that something you can come up with? Alternatively, I can recommend digging into why the assertion fails. This may be quicker than creating a reproduction (or help creating one). It's quite an import assert as it ensure you don't load Vite in production (which is important to avoid memory leaks, among others). |
Thanks again, I really appreciate your recommendation to continue digging into this. After doing just that, I think I've been able to pinpoint the issue around importing Here's the relevant bit from our
When running What's confusing to me is that I'm seeing the
then the assertion error is no longer thrown and the app renders correctly. Is the Sincerely stumped, Allen |
Update: Got it! The
Thank you @brillout again for your help and quick responses! |
Ok neat 👍 I've improved the error message. It should make handling this situation much easier for the user. Btw. would your company be up for sponsoring? It's make a big difference for us! |
Description
Hello, we recently upgraded to vite-plugin-ssr 0.4.142 (we are hoping to tackle the upgrade to Vike at a later time) and started seeing this error when building our app in Github Actions:
Does anyone recognize this as a common issue? Any guidance would be greatly appreciated!
The text was updated successfully, but these errors were encountered: