https://discord.cloudflare.com logo
Join Discord
Powered by
# workers-discussions
  • n
    Anyone use flareact on production? (I dont know if its correct to ask about it on this server)
  • e
    Its Workers related, so the best place! 😄 I am using Flareact for https://status-page.eidam.dev, however its a simple single page app. Do you have something specific on mind?
  • n
    Very nice! Sometimes i built landing page for clients, look like flareact might be a good fit for future project. Thera are many pros already for my use case. Please correct me if i am wrong but the cons will be: 1. Static files limit is 1MB (kv key limit) 2. No simple replacement for next/image (auto optimize image size) Still experimenting with it.
  • p
    the current KV value limit is 25MB iirc
  • p
  • n
    Ah my mistake. Thats very generous
  • e
    And yep, no auto image optimisation unfortunately
  • g
    @User , can I DM you to chat about image optimization?
  • n
    sure @User
  • i
    You could use Cloudflare’s Image Optimization or Cloudflare Image Resizing if you are on Biz or higher.
  • e
    Yep, I am not for my personal projects, however we briefly discussed it with @User and he pointed out that 
    next/image
    can actually be included/used in Flareact just as other npm modules
  • g
    Still needs testing. But 
    next/image
    does support custom loaders, so I'm writing one for Cloudflare Image Resizing right now.
  • i
    That would be so cool.
  • d
    Hi, I have a case where my workers are stochastically timing out on a simple jwt verify routine.. can you offer any insight into why a specific worker could sometimes exceed the time limit
  • g
    Yeah, there's already loaders for Imgix, Akamai and Cloudinary, so it makes sense to add.
  • i
    Yeah, for sure. Note, though. The loader must be within the Worker itself, not using the path because when Workers run, especially if the file is served by the Worker they'll fail.
  • g
    I'm just adding the loader to 
    next/image
    right now, which'll just do URL re-writing.
  • a
    I use imgix and then store the optimized on the fly (with format variations) on KV indefinitely.
  • g
    I spent all summer doing image optimization stuff with Workers though, so perhaps we can write a Worker or Flareact component which specifically leverages all the magic available to Workers (e.g. request Client Hints and the Cloudflare Cache)
  • g
    KV rather than Cache? Any particular reason?
  • a
    with no loaders, just my manipulation
  • a
    S3 Provider > Imgix > KV > Cache
  • a
    I do use cache, but it can be evicted for many reasons
  • g
    More performant than KV though, no?
  • g
    (Assuming cache hit)
  • a
    Yes, but the way I built it, I load 100,000 master images (50 Mb PNG ) on the S3 provider, then as user visits and bots crawl those images are optimized on-demand, optimization goes to cache and KV.
  • a
    No need to re-optimize, only in case of a new format.
  • g
    Ah, fair! I was just curious 🙂
  • a
    As cache is per colo, you still need a source of truth of the optimized, you could put in another S3 bucket, but I opted Cloudflare KV.
  • g
1...666768...2509Latest