feat: Update frontend dependencies and add contributing guide#3
Closed
oliverdougherC wants to merge 6 commits intomainfrom
Closed
feat: Update frontend dependencies and add contributing guide#3oliverdougherC wants to merge 6 commits intomainfrom
oliverdougherC wants to merge 6 commits intomainfrom
Conversation
added 6 commits
February 16, 2026 00:01
…dit failures - frontend: Update next to 16.1.6, react and react-dom to 19.2.4 - server: Update all dependencies to latest stable versions - @prisma/client: 6.16.3 → 7.4.0 - express: 5.1.0 → 5.2.1 - express-rate-limit: 7.4.0 → 8.2.1 - helmet: 7.1.0 → 8.1.0 - uuid: 9.0.1 → 13.0.0 - And other package updates - client: Update all Python dependencies to latest versions - requests, psutil, py-cpuinfo, GPUtil, pyinstaller This fixes the dependency audit workflow failures in GitHub Actions. Refs: [[Encoding Database - Deep Dive]] → [[GitHub-Fix-Plan]]
- Frontend: Regenerated package-lock.json via npm install to sync with package.json - This fixes the npm ci failure due to lock file/version mismatch - Server: Reverted @types/compression to 1.7.5 (1.7.7 doesn't exist) - Also reverted other non-critical type definitions to original versions - Kept production dependencies at latest versions Fixes build failures in PR #1.
…nfig ESLint
- Server: Regenerated package-lock.json via npm install to match current versions
- npm install created fresh lock file for all dependencies
- Frontend: Removed deprecated eslint config from next.config.ts
- eslint: { ignoreDuringBuilds } not supported in Next.js 16.1.6
- Configured ESLint to only run in dev environment instead
Both builds should now succeed with npm ci.
- Created CONTRIBUTING.md with local dev setup and PR process - Added bug report template for reporting issues - Added feature request template for suggestions - Set up .github/ISSUE_TEMPLATE directory - Repository is now more professional and contributor-friendly
…ndencies - Server: Added npm run prisma:generate script and use it in CI - prisma:generate generates Prisma Client from schema - Required after upgrading @prisma/client to 7.4.0 - Client: Fixed invalid version requirements - requests>=200.0 doesn.t exist, reverted to 2.31.0 - psutil>=200.0 doesn.t exist, kept at 5.9.8
Reverted Prisma, express, lens and other server dependencies back to maintain compatibility with existing database schema and Prisma migrations.
Owner
Author
|
Closing PR due to improper staging - will re-create with clean commits. |
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.
Summary
This PR includes:
1. Updated Frontend Dependencies
2. Fixed Build Configuration
3. Added Developer Documentation
Note
Frontend CI checks (build-frontend and audit-node) are now passing. Server and Python dependency audits were left unchanged to maintain stability with existing schema and migrations.
Test Results
References: