Add missing jsdom dev dependency to fix vitest environment #722

[vansh2604-star]

🔗 Related Issue

Closes #722

---

📝 Description of Changes

Added the missing jsdom development dependency to the project's configuration to prevent Vitest from crashing due to an unhandled module resolution error. This environment is required by the textures.test.ts suite.

---

🏷️ Proposed Labels

• UI/UX
• Documentation
• CI/CD
• Backend Logic
• Anything else

---

📂 Core Files Changed

• package.json
• package-lock.json

---

📸 Verification & Screenshots

• UI/UX (User Interface / User Experience - how it looks and feels):
  N/A

• CI/CD (Continuous Integration / Continuous Deployment - the automated build/test pipeline):
  Ran the Vitest suite locally using npm test. All 26 assertions from both kepler.test.ts and textures.test.ts passed successfully without any environment-related module resolution errors:

---

🤖 AI Assistance Declaration

Did you use an AI tool to write or assist with this code OR Pull Request?

• Yes
• No (If no, you can skip the rest of this section)

⚠️ IF YOU CHECKED "YES", YOU MUST ANSWER THE FOLLOWING:

• Which AI Model did you use?: Gemini 3.5 Flash
• Which Platform/Tool?: Antigravity
• What exactly did the AI do?: Identified the missing jsdom package from the package.json configurations, installed it, and verified that both test suites run and pass successfully.
• What exactly did YOU do?: Approved the installation of jsdom, ran the git commands to commit and push the branch, and initiated the PR.
• What is the advantage of using this AI approach here?: Rapidly isolated the missing testing environment dependency and verified the fix.

---

⚠️ Reviewer Notes

The change is minimal, introducing only the jsdom devDependency to fix the test suite crash.

---

✅ The "I Swear I Didn't Break Anything" Pledge

• I have thoroughly tested these changes in my own local branch.
• I verified multiple times that this code compiles into a standalone build and does not break existing production features.
• [ ]

[vercel]

Someone is attempting to deploy a commit to the Sp's projects Team on Vercel.

A member of the Team first needs to authorize it.

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[vansh2604-star]

@Mergifyio queue

[mergify]

queue

☑️ Command disallowed due to command restrictions in the Mergify configuration.

Details

• sender-permission >= write