Repository navigation
chore(deps): update dependencies - #294
Merged
Merged
Conversation
Update dev dependencies and e2e project dependencies to the latest versions published before the 3-day cutoff. Refresh transitive dependencies in the lockfile. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L1dGD8MgqPgHL9xqDmyuuh
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.
This PR updates dependencies to the latest versions published before the 3-day cutoff (2026-11-07).
Updated direct dependencies
npm updatealso refreshed transitive dependencies inpackage-lock.json. For example, tsdown now uses theyukuand@yuku-toolchain/*packages instead ofyuku-core,yuku-parser,yuku-codegen, and@yuku-core/binding-*. Also,@oxc-project/typesmoves 0.155.0 → 0.157.0, and@emnapi/*and@napi-rs/wasm-runtimeare new for the wasm bindings. I used npm 11.21.2 so that the lockfile keeps itslibcfields.Lint, type-check, and build pass locally. The
peerDependenciesranges stay the same, and no source, test, or CI files change. The e2e project keeps its exact-version pins.Build output
I compared
dist/with the build onmaster. tsdown 0.23.7 changes two things:index.jsandindex.d.ts.package.jsonfrompackage.jstopackage.json.js. The content (version = "3.5.1") is the same, and theexportsmap does not expose this chunk.These changes have no effect on behavior or public types.
Not updated
dotenv18.0.10,next16.4.6,oxfmt0.78.0, andoxlint1.93.0 came out after the cutoff. A later run will pick them up.@prismicio/types-internal(3.17.2, latest 4.8.1) is skipped by policy.Held back
None.
🤖 Generated with Claude Code
https://claude.ai/code/session_01L1dGD8MgqPgHL9xqDmyuuh
Note
Low Risk
Routine dependency and lockfile refresh with no runtime code changes; only minor build-tool output reordering from the tsdown upgrade is expected.
Overview
This PR bumps direct dependencies in the root workspace and the
e2e-projects/nextjsapp, then regeneratespackage-lock.jsonvianpm update.Root dev tooling:
@playwright/testandplaywright→^1.65.0,@prismicio/client→^7.23.0,oxfmt→^0.77.0,oxlint→^1.92.0, andtsdown→^0.23.7.E2E Next app:
@prismicio/client→^7.23.0,next→16.4.5, and@types/node→^26.6.6.The lockfile also pulls in newer transitive packages (e.g.
rolldown1.3.0, consolidatedyuku/@yuku-toolchain/*instead of olderyuku-corepackages, and wasm-related@emnapi/*/@napi-rs/wasm-runtimefor bindings). No application or test source files change;peerDependenciesand engine requirements are unchanged.Reviewed by Cursor Bugbot for commit 7f03bdc. Bugbot is set up for automated code reviews on this repo. Configure here.