Refresh app dependencies and pnpm config#1
Draft
what256 wants to merge 1 commit into
Draft
Conversation
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
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.
What changed
Cargo.lockallowBuildsconfigurationWhy
The previous pnpm configuration used
onlyBuiltDependencies, which pnpm 11 no longer reads. That caused clean installs to stop before typechecking or building.Impact
Fresh installs work with the pinned package manager, dependency build scripts remain explicitly scoped, and the application stays on its current React, Tailwind, TypeScript, and Vite major versions.
Validation
pnpm run typecheckpnpm run lintpnpm run buildcargo test --lib --locked— 14 passedgit diff --checkThe full ExifTool integration suite remains Windows-specific and requires the gitignored bundled ExifTool resources.