fix(web): allow external images in Next.js Image component - #6
Conversation
Next.js restricts the `next/image` component to internal domains by default. Configured `next.config.ts` to parse the `NEXT_PUBLIC_S3_ORIGIN` environment variable and add it to `remotePatterns`, alongside Google Auth avatars, to allow uploaded images to be properly optimized and displayed. Also fixed a minor backend spec counting public routes and a nullish content crash in the blog service. Co-authored-by: fdaei <81993335+fdaei@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Next.js Image component needs configured remotePatterns to render images originating from S3 (which the Next app fetches for things like user avatars and course images). Added configuration parsing to next.config.ts.
PR created automatically by Jules for task 9731696446521535187 started by @fdaei