chore: drop unused deps, unpin proxy from beta, tidy package metadata#27
Merged
Conversation
- Remove `cross-fetch` and `console-table-printer` from dependencies: neither is referenced anywhere in server/, app/, or tests/. Removing them also drops their transitive deps (node-fetch, encoding, whatwg-url, etc.) from the tree. - Change `http-proxy-middleware` from `^3.0.0-beta.1` to `^3.0.7` so the example no longer advertises a dependency on a pre-release (the specifier already resolved to stable 3.0.7; no resolved version change). - Fill in the empty `description` and swap the leftover `starter`/`template` scaffold keywords for ones that describe the project. Lint, typecheck, build, and the full test suite (including the live Pinecone e2e) all pass. `npm audit --omit=dev` reports 0 vulnerabilities. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Why
Maintenance hygiene on
package.json— no runtime behavior change.What changed
cross-fetchandconsole-table-printerare declared independenciesbut referenced nowhere inserver/,app/, ortests/(leftover scaffold cruft). Removing them also prunes their transitive deps (node-fetch,encoding,whatwg-url,tr46,webidl-conversions,simple-wcswidth) from the lockfile.http-proxy-middlewarefrom a beta. The specifier was^3.0.0-beta.1, which advertised a dependency on a pre-release even though it resolved to stable3.0.7. Changed to^3.0.7; the resolved version is unchanged, so there's no lockfile churn there.descriptionand replaced the leftoverstarter/templatescaffold keywords with ones that actually describe this project.Testing
npm run lint— passes (one pre-existing, unrelated warning inmain.tsx)npm run typecheck— passesnpm run build:app— passesnpm test— all 50 tests pass, including the live Pinecone e2e (createIndex/upsert/query/deleteOneagainst a real throwaway index)npm audit --omit=dev— 0 vulnerabilities🤖 Generated with Claude Code