Deployed on Netlify, having an +onBeforeRender for a SPA dynamic pages leads to an error

[orangecoloured]

I have some dynamic pages, like path/@index. I used this repo as an example to set up my deployment. It's partially prerendered, and partially rendered on request.

meta for the dynamic pages contains { Page: { client: true } }.
In the +onBeforeRender hook I run a quick data check, testing if the url with the @item exists so I can throw an error page in case it doesn't.
It works well, while I dev locally, but on Netlify it throws a 404 error.

Interesting thing is that the contents of the +onBeforeRender don't matter. I made it an empty function and it still failed. Removing the +onBeforeRender file fixes it, I can access these pages. That's what I did as a temporary fix.

How can I try to debug/fix this?

[phonzammi]

Hi @orangecoloured

I used this repo as an example to set up my deployment

It seems that you're using a very old example (vite-plugin-ssr) with deprecated API design.

Please you should try to migrate to the latest Vike version with V1 Design. You can see migration guide.

[orangecoloured]

From the example I only used this part in my app. The rest is aligned with the latest API design.

[brillout]

I wouldn't know how this could be related to Vike. I'm inclined to think it's some kind of user land quirk.

[orangecoloured]

The project I'm using it for is purely for my personal use and I don't like when having fun experimenting ends up with not having fun stumbling on bugs which I had no idea would be an issue based on the examples/docs that I used while aligning my code with the vike's API.

I ended up with vike only becasue the latest create-preact comes with it. I simply wanted to move my old preact code to the up to date setup. It's not like I was eager to try out vike, I just had to. Your documentation is not clear. And vike is clearly not ready for "production" use. And still you don't miss the opportunity to ask for sponsorship.

I understand that this is not a great comparison, but I can take NextJS and have everything I need with a much better docs, examples and community.

[brillout]

Be my guest and use Next.js instead of Vike. One toxic and narrow minded user less 👌

Edit: I don't feel replying like that anymore, and it isn't how I want nor feel like reacting in the future.

[brillout]

I share the sentiment that using a tool that doesn't seamlessly work is frustrating, and we very much aim to make Vike a seamless tool. (And, again, one of the open PR is actually about addressing the very issue of this thread.)

[orangecoloured]

All good. I'm going to look at svelte for now. I'm using NextJS on daily basis at work and want to try out something else for my personal use so not to lock myself into one setup/environment.

[brillout]

SvelteKit is quite neat indeed.