Repository navigation
chore(deps): bump nine npm packages in one branch - #99
Merged
Merged
Conversation
- Combine dependabot #96 (tailwind, 2), #97 (production, 2) and #98 (development, 5) into one tree; all three touch package.json and package-lock.json, so merging them separately forces a rebase-and-rerun round. - #96 and #97 conflict on adjacent package.json lines, so the lockfile was regenerated on top of #96's lock (the largest tree change: tailwind 4.3.4 dedupes lightningcss and magic-string). - npm drifted lucide-react, oxlint and fake-indexeddb past the versions dependabot locked; they are pinned back, and every lock entry now matches one of the three PRs. Co-Authored-By: htjulia <htjulia1@gmail.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
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 three dependabot PRs into one tree. All three touch
package.jsonandpackage-lock.json, so merging them one by one would force a rebase-and-rerun round for the others.Closes #96
Closes #97
Closes #98
What is bumped
@tailwindcss/vitetailwindcss@tanstack/react-virtuallucide-react@vitejs/plugin-react@vitest/coverage-v8fake-indexeddboxlintvitestHow the lockfile was built
package.jsonlines (and chore(deps-dev): bump the npm-development group with 5 updates #98 conflicts with chore(deps): bump the tailwind group with 2 updates #96 in the lockfile), so a plain merge was not possible.npm installon top of chore(deps): bump the tailwind group with 2 updates #96's lock — the largest tree change. Tailwind 4.3.4 moves tolightningcss1.33 andmagic-string1.x, which removes the nested copies undervite/andvitest/; that dedupe is where most of the −612 lockfile lines come from.lucide-react1.70.0,oxlint1.92.0,fake-indexeddb6.2.8. All three are pinned back to the PR versions (1.68.0 / 1.91.0 / 6.2.7).mainand the three PR lockfiles: 0 entries are left that none of the PRs explains.Verification (local,
npm cifrom this commit)mainnpm run lintnpm run buildnpm testnpx vitest run --coveragenpm auditnpm audit --omit=devreact(immutability), a rule new in oxlint 1.91.0 (use-console-data.ts:515,use-trace-store.ts:218,use-trace-store.ts:252). They are warnings, not errors, and do not fail CI; whether to address them is left for a separate change.--coveragewas run because@vitest/coverage-v8is not exercised bynpm test.mainand are dev-only; this PR does not introduce them.