bug(gatsby-plugin-fastify): Error fetching page data for /using-ssr when pagePrefix is set about plugins HOT 5 OPEN

The many problems with gatsby serve are why this plugin exists.

Okay, I'll try to find some time to look at this.

From my current understanding your current solution shouldn't be correct, the assumption is...if you have a prefix, the non-prefixed path is probably an entirely different server and thus wouldn't be able to handle these routes.

from plugins.

Okay, confirmed. I understand what's happening. potentialPagePath seems like the correct move since we already have that. I'm happy to merge a PR on this if you can get that submitted.

from plugins.

This fix seems incorrect to me...those assets should still be served from /gatsby. Are you following the Gatsby Docs and correctly running the build with gatsby build --prefix-paths?

from plugins.

@moonmeister

Yes, I did!

I am using gatsby build --prefix-paths in order to build with prefixPath. Right now I am serving my app with that configuration and with that minimal change. I would appreciate to you that you can reproduce my issue following my instrucction.

Include the gatsby build --prefix-paths in the script, since I omite mentioned it before.

Note: in fact gatsby serve --prefix-paths has problems using SSR. And your plugin is better than gatsby serve

from plugins.

Thank you for the confirmation! I agree with proceeding with "potentialPagePath". I plan to submit the Pull Request, but I'll do so after the Christmas holidays. I hope you have a wonderful holiday season with your loved ones as well. 🎄☃️

from plugins.