Remove unused music metadata dependencies - #14
Draft
lowan-rtn wants to merge 1 commit into
Draft
Conversation
lowan-rtn
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changed
music-metadatadependencymusic-metadata-browserdependencyWhy
Neither package is imported by the application source, Electron process, or tests. Keeping them in production dependencies increases install size and causes
npm audit --omit=devto report vulnerabilities through the deprecated browser package's transitive dependency chain.Impact
Application behavior is unchanged. Fresh installs avoid downloading 26 unnecessary packages and the production dependency audit is clean.
Validation
npm test— 9 tests passednpm run build— production Vite build succeedednpm audit --omit=dev— 0 vulnerabilities