Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/web/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@
"react": "19.2.8",
"react-dom": "19.2.8",
"recharts": "3.10.1",
"sharp": "0.35.0",
"sharp": "0.35.3",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== apps/web/package.json ==\n'
grep -n '"sharp"' -n apps/web/package.json || true

printf '\n== lockfile sharp references ==\n'
rg -n '"sharp"|sharp@|sharp:' pnpm-lock.yaml apps/web/package.json || true

printf '\n== nearby lockfile context ==\n'
rg -n -C 2 'sharp' pnpm-lock.yaml || true

Repository: jusso-dev/Muster

Length of output: 11755


Regenerate pnpm-lock.yaml for the Sharp bump. The lockfile still pins sharp to 0.35.0 in the override, importer entry, and package resolution, so frozen-lockfile installs can keep resolving the old version or fail against the updated manifest.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/web/package.json` at line 46, Regenerate pnpm-lock.yaml after updating
the sharp dependency to 0.35.3, ensuring the sharp override, importer entry, and
package resolution all consistently reference 0.35.3 so frozen-lockfile installs
match the manifest.

"tailwind-merge": "^3.3.1",
"tailwindcss": "4.3.3",
"zod": "4.4.3"
Expand Down
Loading