"Optimize repeated alias loading in dependency scanner"

[namrarafique93-del]

Summary

Improves dependency scan performance by caching internal aliases instead of repeatedly loading them during every import check.

Closes #1108

Type of Change

• Bug fix
• New feature
• Documentation update
• Refactor / code cleanup

Changes Made

• Moved "loadInternalAliases(cwd)" outside the import loop
• Reused cached aliases during dependency scanning
• Reduced repeated filesystem reads and JSON parsing

How to Test

Steps for the reviewer to verify this works:

1. Run:

node scripts/check-missing-deps.js

2. Verify the script executes successfully without changing existing behavior

3. Confirm aliases are loaded once instead of repeatedly during import scanning

Screenshots (if UI change)

N/A

Checklist

• Linked issue in summary
• "npm run lint" passes locally
• No TypeScript errors ("npm run type-check")
• Self-reviewed the diff
• Added/updated tests if applicable

[vercel]

@namrarafique93-del is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

• level:beginner — 20 pts
• level:intermediate — 35 pts
• level:advanced — 55 pts
• level:critical — 80 pts

Quality (optional):

• quality:clean — ×1.2 multiplier
• quality:exceptional — ×1.5 multiplier

Validation (required to score):

• gssoc:approved — counts for points
• gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

[Priyanshu-byte-coder]

Playwright smoke tests are failing on this PR. Check the CI logs, fix failing tests, then push an update. Cannot merge while tests are red.

[namrarafique93-del]

@Priyanshu-byte-coder Done please review
Thank you !!!!

[github-actions]

🎉 Merged! Thanks for contributing to DevTrack.

If the project has been useful to you, a ⭐ star on the repo is the easiest way to support it — it helps DevTrack get discovered by more developers.

Keep an eye on open issues for your next contribution!