Remove unused jquery-1.11.1.js from external test dependencies #77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes the unused jQuery 1.11.1 library file from the repository as requested in the issue.
Changes Made
common/Tests/External/jquery-1.11.1.js(10,308 lines, ~305KB)Verification
✅ No references found: Comprehensive search confirmed no code references to this specific file anywhere in the codebase
✅ Build system unaffected: Verified that build behavior remains unchanged (any existing build issues are unrelated to this change)
✅ External dependencies maintained: The
common/Tests/External/directory still contains all other necessary test dependencies (QUnit, Sinon, RequireJS, etc.)✅ Minimal change: Only 1 file deleted, 0 lines added - exactly what was requested
Context
The jQuery 1.11.1 file was located in the external test dependencies directory but was not referenced by any build scripts, test files, or source code. While jQuery TypeScript definitions (
jquery.d.ts) remain available in the same directory for any future needs, the actual library file was unused legacy code that could be safely removed.This cleanup reduces the repository size and removes an outdated dependency that could potentially introduce security concerns if ever accidentally used.
Fixes #76.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.