IIS Error Quick Fix Needed

My IIS-hosted web app throws a mapping-related error whenever a JavaScript file runs, so the frontend fails to load correctly. I need someone who can jump in right away, pinpoint the IIS configuration issue, and apply a clean, minimal fix so the error messages disappear and the JS assets serve as expected.

Key points:
• Environment: IIS on Windows, .NET backend, JS-heavy frontend (only the JS layer is currently affected).
• Issue: Error messages appear in the browser console—seems tied to incorrect handler or MIME mapping for a script resource.
• What I expect from you:
– Locate the faulty mapping or handler rule.
– Adjust web.config or IIS settings to restore normal script delivery.
– Validate the fix by reloading the site and confirming no errors in the console.
• Tools you’re comfortable with can include the IIS Manager, web.config editing, remote PowerShell, or any standard .NET diagnostics utilities.

This is a quick, focused task—once the scripts load without errors and the page renders correctly, we’re done. If everything checks out, I’ll close the project and leave prompt feedback.

Console logs the following;
"[Violation] Forced reflow while executing JavaScript took 48ms"