Skip to content

chore(core): drop unused glob and faiss-node dependencies - #416

Open
SomSamantray wants to merge 2 commits into
zilliztech:masterfrom
SomSamantray:fix/377-npm-deprecation-warnings
Open

chore(core): drop unused glob and faiss-node dependencies#416
SomSamantray wants to merge 2 commits into
zilliztech:masterfrom
SomSamantray:fix/377-npm-deprecation-warnings

Conversation

@SomSamantray

Copy link
Copy Markdown

Fresh npm install of the published MCP package no longer emits deprecation warnings for glob and prebuild-install — two of the six warnings a new install reports. Both packages were declared as direct dependencies of @zilliz/claude-context-core but are not imported anywhere in the repository, so removing them is zero-risk and supersedes bumping glob to ^11. The remaining warnings (q, node-domexception, uuid) come from upstream major-version chains (milvus2-sdk-node 2.x, langchain 0.3.x, genai 1.x) and are out of scope without breaking bumps.

Validation: core build, typecheck, and 29/29 tests pass; npm pack of the core tarball followed by a fresh consumer npm install shows both warnings gone.

Related: #377

Session-settled decisions carried from planning: remove unused dependencies instead of bumping them (user-approved, over bumping glob to ^11).


Compound Engineering

…ch#377)

Both packages were declared as direct dependencies of
@zilliz/claude-context-core but are not imported anywhere in the
repository. glob@10 is itself deprecated, and faiss-node pulls in the
deprecated prebuild-install, so removing them clears two of the six
npm warn deprecated lines reported in issue zilliztech#377 for downstream
consumers (verified via npm pack + consumer install). The remaining
warnings (q, node-domexception, uuid) come from upstream major
versions (milvus2-sdk-node 2.x, langchain 0.3.x, genai 1.x) and are
not addressable without breaking bumps.
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.

1 participant