Add a Cloudflare Pages build option (again)

[rmarscher]

We updated our --with-cloudflare build option from Cloudflare Workers to Cloudflare Pages and then back to Cloudflare Pages with Static Assets.

Related:

• How does the config file work? What's the difference between using `waku.config.ts` and/or `vite.config.ts`? #763
• feat: migrate cloudflare workers adapter to cloudflare pages #793
• feat: cloudflare pages adapter, alternate implementation #795
• Switch back to Cloudflare Workers #944
• Switch from Cloudflare Pages to Workers with Static Assets #989

I found that while Cloudflare Pages' advanced mode function and Cloudflare Workers are almost the same, it seems that Cloudflare Pages' advanced mode function runs after Cloudflare's edge cache while a Cloudflare Worker always runs before the cache. cloudflare/cloudflare-docs#20445

For sites that want to do SWR, it can be better to leverage Cloudflare's cache rules instead of using Cloudflare's cache API from within a worker.

[dai-shi]

If it's a long-term decision, we could separate two options: ---with-cloudflare-workers and --with-cloudflare-pages
Isn't the plan to integrate Workers and Pages in the future?

And, it depends on how much percentage of waku + cloudflare users need Pages.

Another option is to allow a user-defined deploy adapter.

[rmarscher]

Another option is to allow a user-defined deploy adapter

Could it be possible to pass a string in cli and then attempt to load that? Similar to the new string middleware config?

waku build --with-adapter './my-build-adapter'

That would work with a local ./my-build-adapter.ts in the root of my project and also open up for community waku build adapters hosted on npm.

[dai-shi]

Yeah, I like the custom build plugin approach.

Actually, it should already be possible with unstable_viteConfigs in waku.config.ts or vite.config.ts.
Would you give it a try and see if you face any problems?