Nicholai
1be512f658
🐛 Bug Fix: The Next.js <Image> component requires Node.js APIs that aren't available in Cloudflare Workers runtime, causing 'Image constructor: new is required' errors. Changes: - Revert hero-section.tsx to use background-image CSS - Revert artists-section.tsx to use native <img> tags - Add loading='lazy' attributes for native lazy loading - Keep images.unoptimized: true in next.config.mjs - Add clear comment explaining Cloudflare compatibility requirement ✅ What's Still Working: - All SEO improvements (metadata, Open Graph, Twitter Cards) - JSON-LD structured data (LocalBusiness, Organization) - Canonical URLs on all pages - Font preloading - Page-specific metadata Note: Native <img> tags with loading='lazy' provide basic optimization without requiring Next.js Image APIs. For Cloudflare R2 image optimization, consider using Cloudflare Images service separately. Issue: #GH-419 (React error) Platform: Cloudflare Workers
18 lines
402 B
JavaScript
18 lines
402 B
JavaScript
/** @type {import('next').NextConfig} */
|
|
const nextConfig = {
|
|
eslint: {
|
|
ignoreDuringBuilds: true,
|
|
},
|
|
typescript: {
|
|
ignoreBuildErrors: true,
|
|
},
|
|
images: {
|
|
// Must be unoptimized for Cloudflare Workers compatibility
|
|
// Next.js Image component requires Node.js APIs not available in Workers runtime
|
|
unoptimized: true,
|
|
},
|
|
output: "standalone",
|
|
}
|
|
|
|
export default nextConfig
|