Fix ESM Compatibility Issue in Next.js Config

[devin-ai-integration]

Fix ESM Compatibility Issue in Next.js Config

Overview

This PR fixes the ESM compatibility issue in the Next.js configuration that was causing Netlify builds to fail.

Changes

• Updated cache-handler.js to use ES module syntax (import/export) instead of CommonJS (require/module.exports)
• Fixed next.config.mjs to use a direct path reference instead of require.resolve()

Problem Solved

This fixes the following error in Netlify builds:

ReferenceError: require is not defined in ES module scope, you can use import instead

Testing

• Verified the ES module syntax is compatible with Next.js configuration
• Ensured compatibility with the existing Netlify deployment process

Link to Devin run

https://app.devin.ai/sessions/b7438232b1c14149ad0c12f9c7b384ef

Requested by: Ilya Paveliev ([email protected])

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
uorcontent	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	May 10, 2025 11:39am
v0-uor-mcp	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	May 10, 2025 11:39am

[netlify]

👷 Deploy Preview for uor-content processing.

Name	Link
🔨 Latest commit	28120ce
🔍 Latest deploy log	https://app.netlify.com/sites/uor-content/deploys/681f3aff1748280009232f22

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring