Traffisco

Try a temporary workaround, go to cloudflare panel and set the flareact worker on the public route. eg `http://yourdomain.com/public` Should work

> * How can I reproduce this issue? import a big enough library to be splitted by webpack. Can’t think of an example, I used my own library when discovered....

Trailing / could be auto stripped https://github.com/flareact/flareact/blob/7f931cabac0bbd1bc2bfe1c06f624bd7f98beb46/src/worker/worker.js#L64

Why use getEdgeProps if you want to render on the client?

> > Why use getEdgeProps if you want to render on the client? > > Because I want to have SSR when the URL is directly accessed. So basically, you...

> > So basically, you want the first load to be served from cache then, skip getEdgeProps on navigation and run it on the client? > > I'm also not...

> > Wouldn't it be easier then to do a hard navigation then? > > I'm sorry, I don't understand your question. I propose to perform a hard navigation when...

> errr... let me be more clear. > > Right now, the behavoir is that if you have `getEdgeProps()` on a route and you navigate to it from a different...

> > I think that this only happens if you use flareact Link with prefetch on. When landing on a cached route(directly or with hard navigation) you just get rendered...

Another option is to hard navigate to a dynamic route url, SSR will be dynamic based on that url