Skip to content

Drop tagify's React peer dependencies from the lockfile - #11

Merged
codeling merged 3 commits into
mainfrom
claude/exciting-cannon-rb5na8
Oct 2, 2026
Merged

codeling merged 3 commits into
mainfrom
claude/exciting-cannon-rb5na8

Conversation

@codeling

@codeling codeling commented Oct 2, 2026

Copy link
Copy Markdown
Owner

Summary

package-lock.json listed react, react-dom, scheduler, prop-types, react-is, object-assign, loose-envify and js-tokens. None of them are in package.json or vendor/. They came from @yaireo/tagify, which declares react, react-dom and prop-types as peer dependencies for its optional React wrapper. npm 7+ installs peer dependencies automatically.

The app only uses the plain tagify.js build, and scripts/vendor.sh copies only specific files from jQuery, jQuery UI and tagify into vendor/. So the React packages are never used.

Changes

  • Add .npmrc with legacy-peer-deps=true so npm stops auto-installing peer dependencies.
  • Regenerate package-lock.json. It loses 79 lines, all belonging to the eight packages above. @yaireo/tagify, jquery and jquery-ui are unchanged.

Testing

  • npm ci installs only @yaireo/tagify, jquery and jquery-ui, with no errors.
  • vendor/ is unaffected, since the files copied from those three packages haven't changed.

🤖 Generated with Claude Code

https://claude.ai/code/session_015MLMxgPeAFvdgNaGuUFQsK


Generated by Claude Code

claude and others added 3 commits October 2, 2026 19:50
Set legacy-peer-deps so npm no longer installs react, react-dom and their
transitive packages, which the plain tagify.js build does not use.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015MLMxgPeAFvdgNaGuUFQsK
@codeling
codeling force-pushed the claude/exciting-cannon-rb5na8 branch from 9f4d3de to db07c77 Compare October 2, 2026 20:22
@codeling
codeling merged commit 8e53a6c into main Oct 2, 2026
11 checks passed
@codeling
codeling deleted the claude/exciting-cannon-rb5na8 branch October 2, 2026 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants