Skip to content

chore: package upgrades#6278

Merged
KevinVandy merged 4 commits into
alphafrom
package-upgrades
May 21, 2026
Merged

chore: package upgrades#6278
KevinVandy merged 4 commits into
alphafrom
package-upgrades

Conversation

@KevinVandy
Copy link
Copy Markdown
Member

@KevinVandy KevinVandy commented May 20, 2026

🎯 Changes

✅ Checklist

  • I have followed the steps in the Contributing guide.
  • I have tested this code locally with pnpm test:pr.

Summary by CodeRabbit

  • Chores
    • Bumped pnpm package manager version across project manifests.
    • Updated dev tooling and type packages (Node types, @types/react, vue-tsc, vitest, ESLint plugin).
    • Updated example dependencies (Svelte, date-fns, Angular CDK, UI libs, and TanStack query/virtual packages).
    • Routine maintenance to keep examples and tooling compatible with recent releases.

Review Change Stack

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 20, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 54478d3d-8419-4277-ac0b-0eb21cb99ebd

📥 Commits

Reviewing files that changed from the base of the PR and between 1e53e72 and eac42a6.

📒 Files selected for processing (1)
  • examples/svelte/virtualized-infinite-scrolling/package.json

📝 Walkthrough

Walkthrough

Bumps many example and package dependency/version pins (pnpm packageManager, framework runtimes, TanStack libs, type defs) and updates workspace trustPolicy exclusions.

Changes

Dependency version bumps across all examples and packages

Layer / File(s) Summary
Root package manager and devtools updates
package.json, pnpm-workspace.yaml
Updates packageManager to pnpm@11.1.3, bumps @types/node and vitest, and adds trustPolicyExclude to workspace config.
Angular examples and deps
examples/angular/*/package.json
Bumps Angular example packageManager entries to pnpm@11.1.3; updates @angular/cdk and @types/node in specific Angular examples.
React examples and deps
examples/react/*/package.json, packages/react-table*/package.json
Bumps @types/react across React examples and core packages; updates example-specific deps (@tanstack/react-*, date-fns, postcss, etc.).
Svelte examples and package
examples/svelte/*/package.json, packages/svelte-table/package.json
Bumps svelte devDependency to ^5.55.9 and related @tanstack/svelte-* example deps.
Vue examples and deps
examples/vue/*/package.json
Bumps dev tooling (@types/node, vue-tsc) and updates @tanstack/vue-* where present.
Lit, Preact, Solid, Vanilla examples
examples/lit/*, examples/preact/*, examples/solid/*, examples/vanilla/*
Patch bumps for @tanstack/* libs and minor dev dependency updates.
All other example metadata updates
examples/*/*/package.json
Various minor dependency/devDependency patch bumps across examples (type defs, virtual libs, query libs).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested reviewers

  • schiller-manuel

🐰 Dependencies hop and sway,

Versions nudged, then on their way,
pnpm, svelte, React types too—
A rabbit cheers the repo through. 🐇✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'chore: package upgrades' accurately summarizes the primary change across the entire changeset: systematic updates to multiple package dependencies throughout the project.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch package-upgrades

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@nx-cloud
Copy link
Copy Markdown

nx-cloud Bot commented May 20, 2026

View your CI Pipeline Execution ↗ for commit eac42a6

Command Status Duration Result
nx affected --targets=test:eslint,test:sherif,t... ✅ Succeeded 53s View ↗
nx run-many --targets=build --exclude=examples/** ✅ Succeeded <1s View ↗

☁️ Nx Cloud last updated this comment at 2026-05-21 20:54:39 UTC

@socket-security
Copy link
Copy Markdown

socket-security Bot commented May 20, 2026

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Publisher changed: npm content-type is now published by blakeembrey

Author: blakeembrey

From: pnpm-lock.yamlnpm/express@5.2.1npm/content-type@2.0.0

ℹ Read more on: This package | This alert | What is unstable ownership?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/content-type@2.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm svelte is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: examples/svelte/basic-app-table/package.jsonnpm/svelte@5.55.9

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/svelte@5.55.9. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Publisher changed: npm type-is is now published by blakeembrey

Author: blakeembrey

From: pnpm-lock.yamlnpm/express@5.2.1npm/type-is@2.1.0

ℹ Read more on: This package | This alert | What is unstable ownership?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/type-is@2.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Medium
Low adoption: npm eslint-plugin-react-jsx

Location: Package overview

From: pnpm-lock.yamlnpm/@eslint-react/eslint-plugin@5.8.3npm/eslint-plugin-react-jsx@5.8.3

ℹ Read more on: This package | This alert | What are unpopular packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Unpopular packages may have less maintenance and contain other problems.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/eslint-plugin-react-jsx@5.8.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Copy link
Copy Markdown

@nx-cloud nx-cloud Bot left a comment

Choose a reason for hiding this comment

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

Important

At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.

Nx Cloud is proposing a fix for your failed CI:

We fix the table:test:sherif failure by restoring alphabetical order of devDependencies in examples/svelte/virtualized-infinite-scrolling/package.json. The package upgrade PR accidentally placed @tanstack/svelte-virtual before @tanstack/svelte-table, which violates the workspace's sherif unordered-dependencies rule. Swapping the two entries back into alphabetical order (table before virtual) resolves the failure while preserving all updated version numbers.

Warning

  • We could not verify this fix.
  • The suggested diff is too large to display here, but you can view it on Nx Cloud ↗

Apply fix via Nx Cloud  Reject fix via Nx Cloud


Or Apply changes locally with:

npx nx-cloud apply-locally Grjw-TPw8

Apply fix locally with your editor ↗   View interactive diff ↗



🎓 Learn more about Self-Healing CI on nx.dev

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented May 21, 2026

More templates

@tanstack/angular-table

npm i https://pkg.pr.new/TanStack/table/@tanstack/angular-table@6278

@tanstack/lit-table

npm i https://pkg.pr.new/TanStack/table/@tanstack/lit-table@6278

@tanstack/match-sorter-utils

npm i https://pkg.pr.new/TanStack/table/@tanstack/match-sorter-utils@6278

@tanstack/preact-table

npm i https://pkg.pr.new/TanStack/table/@tanstack/preact-table@6278

@tanstack/preact-table-devtools

npm i https://pkg.pr.new/TanStack/table/@tanstack/preact-table-devtools@6278

@tanstack/react-table

npm i https://pkg.pr.new/TanStack/table/@tanstack/react-table@6278

@tanstack/react-table-devtools

npm i https://pkg.pr.new/TanStack/table/@tanstack/react-table-devtools@6278

@tanstack/solid-table

npm i https://pkg.pr.new/TanStack/table/@tanstack/solid-table@6278

@tanstack/solid-table-devtools

npm i https://pkg.pr.new/TanStack/table/@tanstack/solid-table-devtools@6278

@tanstack/svelte-table

npm i https://pkg.pr.new/TanStack/table/@tanstack/svelte-table@6278

@tanstack/table-core

npm i https://pkg.pr.new/TanStack/table/@tanstack/table-core@6278

@tanstack/table-devtools

npm i https://pkg.pr.new/TanStack/table/@tanstack/table-devtools@6278

@tanstack/vue-table

npm i https://pkg.pr.new/TanStack/table/@tanstack/vue-table@6278

@tanstack/vue-table-devtools

npm i https://pkg.pr.new/TanStack/table/@tanstack/vue-table-devtools@6278

commit: eac42a6

@KevinVandy KevinVandy merged commit 3570290 into alpha May 21, 2026
9 of 10 checks passed
@KevinVandy KevinVandy deleted the package-upgrades branch May 21, 2026 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant