chore: configure environment and update image domains

[mishraa-G]

chore: configure environment and update image domains

Related Tickets & Documents

Fixes: #3635

Description

• Updated Next.js configuration to use the modern and secure images.remotePatterns instead of the deprecated images.domains.

Changes

• Modified next.config.js to replace images.domains array with images.remotePatterns for keploy.io, wp.keploy.io, secure.gravatar.com, and pbs.twimg.com.
• Updated package-lock.json via npm install to ensure dependency consistency.

Type of Change

• Chore (maintenance, refactoring, tooling updates)
• Bug fix (non-breaking change that fixes an issue)
• New feature (change that adds functionality)
• Breaking Change (may require updates in existing code)
• UI improvement (visual or design changes)
• Performance improvement (optimization or efficiency enhancements)
• Documentation update (changes to README, guides, etc.)
• CI (updates to continuous integration workflows)
• Revert (undo a previous commit or merge)

Testing

• Ran npm run dev and verified the application starts without errors on localhost:3000.
• Verified that the site redirects to /blog and renders the homepage content successfully including images.
• Ran npm run build to confirm there are no compile-time errors.

Demo

• Confirmed page load via browser automation (screenshots available in local artifacts if needed). No visual design changes were made.

Environment and Dependencies

• New Dependencies: None.
• Configuration Changes: None.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added corresponding tests
• I have run the build command to ensure there are no build errors
• My changes have been tested across relevant browsers/devices
• For UI changes, I've included visual evidence of my changes

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[amaan-bhati]

Hey @mishraa-G Thanks for raising the pr, before i try and review everything on the local, can you please add some preview and checks in the form of screenshots. This would add more context to the pr.

[mishraa-G]

Hey @mishraa-G Thanks for raising the pr, before i try and review everything on the local, can you please add some preview and checks in the form of screenshots. This would add more context to the pr.

Sure @amaan-bhati , Ive atached a screenshot where on launching locally gives deprecation warnings in the console. And i've also attached screenshot of after the fix where there is no deprecation warnings in the console also a screen shot of blog running locally and still loading all the images perfectly after the fix.

before

after

blog thumbnails and external images are loading correctly

[amaan-bhati]

Hey @mishraa-G Please update the pr description adding explanation for the changes added in the package-lock.json.

[mishraa-G]

ohh, thanks for catching that! I ran npm install locally to set up the project and it must have auto-updated the lockfile. That was unintentional. I will revert package-lock.json now to keep this PR focused solely on the config fix if thats okay with you?