-
-
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
You stumbled upon a bug - renderPage function when migrating from version 0.4.150 to 0.4.151 #1404
Comments
Do you get this with 0.4.153?
…On Tue 2. Jan 2024 at 15:56, gasparearmato6991 ***@***.***> wrote:
Description
Hello! We just stumbled on a bug upgrading Vike to version 0.4.151, it's
working fine with the 0.4.150 but it's not with all the newer versions (we
also tried with the latest one, the 0.4.153)
`
Error: ***@***.***[Bug] You stumbled upon a bug in Vike's source code.
Go to https://github.com/vikejs/vike/issues/new and copy-paste this
error; a maintainer will fix the bug (usually under 24 hours).
at
file:///Users/username/Desktop/org/repos/repo/node_modules/vike/dist/esm/node/runtime/globalContext/loadImportBuild.js:16:13
at autoRetry
(file:///Users/username/Desktop/org/repos/repo/node_modules/vike/dist/esm/utils/autoRetry.js:9:19)
at async loadImportBuild
(file:///Users/username/Desktop/org/repos/repo/node_modules/vike/dist/esm/node/runtime/globalContext/loadImportBuild.js:15:9)
at async initGlobalContext
(file:///Users/username/Desktop/org/repos/repo/node_modules/vike/dist/esm/node/runtime/globalContext.js:75:30)
at async renderPageAndPrepare
(file:///Users/username/Desktop/org/repos/repo/node_modules/vike/dist/esm/node/runtime/renderPage.js:66:9)
at async renderPage_wrapper
(file:///Users/username/Desktop/org/repos/repo/node_modules/vike/dist/esm/node/runtime/renderPage.js:26:24)
at async renderPage
(file:///Users/username/Desktop/org/repos/repo/node_modules/vike/dist/esm/node/runtime/renderPage.js:46:50)
at async file:///Users/username/Desktop/org/repos/repo/dist/index.js:220:27
`
And our index.ts looks like that:
`
import express from "express";
import {renderPage} from "vike/server";
async function startServer(): Promise {
const app = express()
app.get("*", async (req, res, next) => {
const pageContextInit = {
urlOriginal: req.originalUrl,
environment: {
CUSTOM_ENV_VAR: "VALUE",
}
};
const pageContext = await renderPage(pageContextInit);
})
}
startServer();
`
We are using Vike with Svelte if it can be useful.
—
Reply to this email directly, view it on GitHub
<#1404>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHVQRXP7MYURMQRE7KLIATYMQNYPAVCNFSM6AAAAABBKER2KOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3DENJTGUYTCNQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
No, the error is appearing when we switch from 0.4.150 to 0.4.151 but even trying with a newer version (e.g. 0.4.152 or 0.4.153 it does not work) |
If you increase the timeout from |
Unfortunately no, it just start retrying more and more times until it reaches the |
That's quite unexpected. I'll need a reproduction, ideally a minimal one although it doesn't have to. |
Fix pre-released in |
Also, would your company be up for sponsoring? |
Description
Hello! We just stumbled on a bug upgrading Vike to version 0.4.151, it's working fine with the 0.4.150 but it's not with all the newer versions (we also tried with the latest one, the 0.4.153)
And our
index.ts
looks like that:We are using Vike with Svelte if it can be useful.
The text was updated successfully, but these errors were encountered: