Repository navigation
chore(deps): bump eight npm packages in one branch - #104
Merged
Merged
Conversation
- Combine dependabot #100 (tailwind, 2), #101 (production, 1), #102 (development, 4) and #103 (jsdom 31, 1) into one tree; all four touch package.json and package-lock.json, so merging them separately forces a rebase-and-rerun round. - #102 and #103 conflict on adjacent package.json lines, so the lockfile was regenerated on top of #103's lock (the jsdom major, the largest tree change). - npm drifted lucide-react, postcss, enhanced-resolve and tapable past the versions the PRs locked; they are pinned back, and every lock entry now matches main or one of the four PRs. Closes #100 Closes #101 Closes #102 Closes #103 Co-Authored-By: htjulia <[email protected]>
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.
Combines four dependabot PRs into one tree. All four touch
package.jsonandpackage-lock.json, so merging them one by one would force a rebase-and-rerun round for the others.Closes #100
Closes #101
Closes #102
Closes #103
What is bumped
@tailwindcss/vitetailwindcss^4.3.3unchanged)lucide-react@vitejs/plugin-reactfake-indexeddboxlintvitejsdomjsdom 31 (major)
jsdomis only used as the vitest test environment. Its breaking changes, checked against this repo:canvasto@napi-rs/canvas— neither is installed here, and no source file uses canvas.JSDOMconstructor may return a partial document — the tests use vitest's environment, not theJSDOMconstructor directly.node ^22.22.2 || ^24.15.0 || >=26.0.0— CI usesnode-version: "22"(latest 22.x), so this is satisfied.How the lockfile was built
package.jsonlines, so a plain merge was not possible (chore(deps): bump the tailwind group with 2 updates #100 and chore(deps): bump lucide-react from 1.68.0 to 1.72.0 in the npm-production group #101 merged cleanly).npm installon top of chore(deps-dev): bump jsdom from 30.1.3 to 31.0.0 #103's lock — the jsdom major, the largest tree change (−162 lockfile lines on its own).lucide-react1.73.0,postcss8.5.33,enhanced-resolve5.27.0,tapable2.3.4. All four are pinned back to the PR ormainversions (1.72.0 / 8.5.32 / 5.26.1 / 2.3.3).mainand the four PR lockfiles: 0 entries are left that none of them explains.Verification (local,
npm cifrom this commit)mainnpm run lintnpm run buildnpm testnpx vitest run --coveragenpm auditnpm audit --omit=devvite)/,/src/main.tsx,/src/App.tsx(200)react(immutability)warnings that 1.91.0 introduced in chore(deps): bump nine npm packages in one branch #99 (use-trace-store.ts:218,:252, anduse-console-data.ts), hence 10 → 7. No source change was needed.mainand are dev-only; this PR does not introduce them.