Hey everyone does anyone know where can I read about multi tenant project with cloud flare and nextj
Hey everyone does anyone know where can I read about multi tenant project with cloud flare and nextjs
17 Replies
anyone tried nextjs 15 on pages?
Not yet supported, only 13 and 14 are so far -> https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/supported-features/
yeah I saw is not supported, but didnt expect it either to be officially listed considering it's so new
Well, then try out and find out?
ye I will probably do, just trying 14 for now. Then will see
There are some neat things is 15, but I think I'll wait until React 19 is out
I was using canary already for some other project I have on remix and was thinking giving it a shot
is normal that my deploy appear on the pages.dev subdomain but not on the linked domain yet (linked domain appear as active already on the pages dashboard of cloudflare)
Not tried pages yet, but for simple static asset only worker I know this works to deploy a static website ->
yeah specially canary, "use cache" looks dope
Something is off with my deploy It only works when I have the log streaming enabled o.O
Might be hard for me to phrase it for you (it means that note would include a statement about where those products are heading in terms of support - which is usually something that triggers internal discussions around the phrasings 😅). But feeling helpful I tried. Realized it's hard not to turn it into a deprecation notice though, but it's still nice to be open with this info to all the users from the beginning, so putting a PR for the last suggestion: https://github.com/cloudflare/cloudflare-docs/pull/17788
"We will continue support this solution, but our long-term support and new development will focus on deploying Next.js apps to..." messes up the meaning of the original phrasing though, but it'll change anyway before the PR get's merged, it always does 🙂
GitHub
Update get-started.mdx by hsnilsson · Pull Request #17788 · cloudfl...
Summary
People starting out new projects should easily see where the support for different products are heading. To avoid some friction. Got this info from the next-on-pages discord and it was sugg...
https://github.com/cloudflare/cloudflare-docs/pull/17788 You can help phrase it better (or completely different) by commenting on the PR I did now.
@fry69 lol I forgot I used next15 xD
guess that's the issue
I did but i'm having errors due to some static routes not being able to be build with next on pages
Cloudflare asked me to export const runtime = "edge" in order to run my api routes, and after adding them it still won't build and gives the same errors: