⬆️ Chore: pnpm up --latest #1512
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
|
WalkthroughThis pull request introduces a new submodule named blockhead and updates dependency versions across numerous package configuration files. Changes span various directories such as bundler packages, CLI tools, docs, examples, extensions, LSP tools, root packages, and tests. In each file, dependency and devDependency version numbers are incremented to newer releases, ensuring consistency and maintenance across the project. Changes
📜 Recent review detailsConfiguration used: CodeRabbit UI ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (38)
🚧 Files skipped from review as they are similar to previous changes (37)
⏰ Context from checks skipped due to timeout of 90000ms (7)
🔇 Additional comments (2)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
docs/node/package.json (1)
13-17: Inconsistent React Versioning Across Dependencies and PeerDependencies.
The dependency updates for"react": "^19.0.0"and"react-dom": "^19.0.0"look good; however, note that thepeerDependenciesstill specify"react": "^18.2.0"and"react-dom": "^18.2.0". Please ensure this mismatch is intentional. If full React 19 support is intended, update the peer dependencies accordingly to prevent potential version conflicts.experimental/viem-effect/package.json (1)
119-129: Comprehensive Dependency Upgrades Require Thorough Testing.
Multiple core dependencies such as"@adraffy/ens-normalize","@effect/schema","@noble/curves","@noble/hashes","@scure/bip32","@scure/bip39","abitype","effect","isows", and"ws"have been updated. Given these significant bumps (especially in@effect/schemaandeffect), please run end-to-end tests to ensure that there are no inadvertent breaking changes in behavior.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (42)
.gitmodules(1 hunks)blockhead(1 hunks)bundler-packages/base-bundler/package.json(1 hunks)bundler-packages/bun/package.json(1 hunks)bundler-packages/bundler-cache/package.json(1 hunks)bundler-packages/compiler/package.json(1 hunks)bundler-packages/config/package.json(1 hunks)bundler-packages/resolutions/package.json(1 hunks)bundler-packages/runtime/package.json(1 hunks)bundler-packages/solc/package.json(1 hunks)bundler-packages/unplugin/package.json(1 hunks)bundler-packages/whatsabi/package.json(1 hunks)cli/package.json(2 hunks)configs/tsupconfig/package.json(1 hunks)docs/bundler/package.json(1 hunks)docs/node/package.json(1 hunks)examples/bun/package.json(1 hunks)examples/esbuild/package.json(1 hunks)examples/next/package.json(1 hunks)examples/svelte-ethers/package.json(1 hunks)examples/vite/package.json(1 hunks)experimental/revm/package.json(1 hunks)experimental/schemas/package.json(1 hunks)experimental/solc/package.json(1 hunks)experimental/viem-effect/package.json(1 hunks)extensions/ethers/package.json(1 hunks)extensions/viem/package.json(1 hunks)lsp/lsp/package.json(1 hunks)lsp/ts-plugin/package.json(1 hunks)lsp/vscode/package.json(1 hunks)package.json(1 hunks)packages/actions/package.json(1 hunks)packages/effect/package.json(1 hunks)packages/jsonrpc/package.json(1 hunks)packages/logger/package.json(1 hunks)packages/server/package.json(2 hunks)packages/state/package.json(1 hunks)packages/utils/package.json(1 hunks)test/bench/package.json(1 hunks)test/mdt-repro/package.json(1 hunks)test/test-utils/package.json(1 hunks)tevm/package.json(1 hunks)
✅ Files skipped from review due to trivial changes (6)
- blockhead
- packages/state/package.json
- packages/utils/package.json
- test/mdt-repro/package.json
- examples/bun/package.json
- lsp/ts-plugin/package.json
⏰ Context from checks skipped due to timeout of 90000ms (7)
- GitHub Check: Nx Cloud Agents (6)
- GitHub Check: Nx Cloud Agents (2)
- GitHub Check: Nx Cloud Agents (4)
- GitHub Check: Nx Cloud Agents (5)
- GitHub Check: Nx Cloud Agents (1)
- GitHub Check: Nx Cloud Agents (3)
- GitHub Check: Nx Cloud - Main Job
🔇 Additional comments (57)
.gitmodules (1)
7-9: New Submodule Entry: "blockhead" AddedThe new submodule entry for "blockhead" is correctly defined with an appropriate path (
blockhead) and URL (git@github.com:darrylyeo/blockhead.git). Please ensure that using the SSH URL aligns with your CI/CD or deployment environments (they might require HTTPS if SSH keys are not configured). Overall, this change meets the requirements for adding a new submodule.configs/tsupconfig/package.json (1)
42-45: Dependency Version Update Verified.
The update of"@types/node"to^22.13.5is consistent with the broader project updates. Please confirm that any type-related issues in your build or IDE integrations are resolved.bundler-packages/whatsabi/package.json (1)
64-64: Dependency Version Update.
The upgrade of"@shazow/whatsabi"to^0.19.0has been noted. Please ensure that no breaking changes were introduced that might affect dependent modules or runtime behavior.packages/logger/package.json (1)
65-67: Logger Dependency Update Confirmed.
The update of the"pino"dependency to^9.6.0is appropriate and aligns with similar dependency updates across the repository. A quick review of its changelog for any breaking changes is recommended.packages/jsonrpc/package.json (1)
67-69: JSONRPC Dependency Update Verified.
The version bump of"@ponder/utils"to^0.2.3maintains consistency with other parts of the project. Ensure that dependent tests and scripts run successfully after this update.extensions/viem/package.json (1)
84-86: Development Dependency Update.
Upgrading"abitype"from^1.0.6to^1.0.8in devDependencies harmonizes with similar updates in adjacent packages. This should provide you with the latest features and bug fixes.bundler-packages/solc/package.json (1)
67-70: Updated Dependency Versions in devDependenciesThe
"abitype"dependency has been bumped to^1.0.8and"solc"to0.8.28, which aligns with our overall dependency update objective. Please verify that these new versions are compatible with the rest of the system.extensions/ethers/package.json (1)
78-78: Updated Ethers Dependency Version in devDependenciesThe
"ethers"dependency has been updated to^6.13.5. This update is consistent with similar changes across the monorepo—ensure that its integration with the peer dependency (i.e.ethers >6.0.0) remains seamless.tevm/package.json (1)
452-455: Updated Core DependenciesThe versions for
"commander"(^13.1.0),"effect"(3.13.2),"glob"(^11.0.1), and"solc"(^0.8.28) have been updated. These changes are a part of the systematic dependency upgrade. Please review downstream impacts, particularly any breaking changes these new versions might introduce.packages/actions/package.json (2)
82-82: Updated 'zod' Dependency VersionThe
"zod"dependency has been updated to^3.24.2. This update is consistent with similar upgrades in the project. No further action is needed unless compatibility issues arise.
88-88: Updated 'abitype' Dependency VersionThe
"abitype"dependency is now at^1.0.8, ensuring uniformity across the repo. Please verify that all modules using this dependency behave as expected.bundler-packages/runtime/package.json (1)
68-73: Updated Dependencies in Runtime PackageBoth
"effect"and"abitype"have been updated to"3.13.2"and^1.0.8, respectively. This modification supports our overall goal of standardizing dependency versions. Ensure these updates are adequately validated against the runtime features.bundler-packages/bun/package.json (2)
68-69: Dependency Updates: "effect" & "solc" Versions
The versions for"effect"and"solc"have been updated to"3.13.2"and"0.8.28"respectively. This change aligns with the overall coordinated upgrade strategy across the repository.
75-75: Dev Dependency Update: "bun-types" Version
The"bun-types"package version is updated to"^1.2.3", which is consistent with recent updates in similar modules. Please ensure that no breaking changes or type definition issues arise in the build process.experimental/schemas/package.json (2)
67-68: Dependency Updates: "@effect/schema" & "effect"
The updates to"@effect/schema"(now"0.75.5") and"effect"(now"3.13.2") are in line with the repository-wide upgrades. It is recommended to verify compatibility with any consumers of these libraries within the project.
73-73: Dev Dependency Update: "viem" Version
Upgrading"viem"to"^2.23.5"ensures consistency with similar dependency bumps found elsewhere. Make sure that any tooling or test scripts relying on"viem"continue to operate as expected.test/bench/package.json (2)
68-69: Core Dependency Updates: "typescript" & "wagmi"
The bump of"typescript"to"^5.7.3"and"wagmi"to"^2.14.12"reflects a consistent update strategy. Please run the full test suite to ensure that these upgrades do not introduce any type-checking or runtime issues.
74-74: Dev Dependency Update: "@types/node"
The version of"@types/node"is updated to"^22.13.5", matching the changes made elsewhere in the repository. Confirm that no discrepancies occur in type definitions across platforms.bundler-packages/base-bundler/package.json (1)
73-75: Dependency Version Alignment: "@types/node", "effect", & "solc"
The updates to"@types/node"("^22.13.5"),"effect"("3.13.2"), and"solc"("0.8.28") bring this package in line with the global dependency upgrade effort. Please ensure that downstream projects consuming this package are also compatible with these versions.packages/server/package.json (2)
74-74: Dependency Update: "zod" Version
The upgrade of"zod"to"^3.24.2"is consistent with similar changes in other package files. Verify that any schema validations relying on"zod"maintain their expected behavior post-update.
83-84: Dev Dependency Updates: "express" & "next" Versions
The updates to"express"("^4.21.2") and"next"("^15.1.7") in the devDependencies section reflect the latest patches. It is advisable to test server configurations and related Next.js functionalities to ensure a smooth transition.packages/effect/package.json (2)
61-63: Dependency Version Updates (effect and resolve)
The dependencies"effect"and"resolve"have been updated to"3.13.2"and"^1.22.10", respectively. This aligns with the maintained upgrade strategy across the project. Please verify that any consumers of these dependencies remain compatible with the updated versions.
68-68: Dev Dependency Update (@types/node)
The dev dependency"@types/node"has been bumped to"^22.13.5". Ensure that the new type definitions do not introduce any conflicts or unexpected type behavior in projects consuming this package.test/test-utils/package.json (2)
67-67: Dev Dependency Update (@types/node)
The update of"@types/node"to"^22.13.5"is consistent with changes elsewhere in the repository. Please double-check that the tests and fixtures in this package continue to run correctly under the new definitions.
73-74: Major Dependency Upgrades (@openzeppelin/contracts and @ponder/utils)
The dependency"@openzeppelin/contracts"has been upgraded to"5.2.0"(a major version bump) while"@ponder/utils"has been updated to"^0.2.3". Major version changes can sometimes introduce breaking changes. It is advisable to review the release notes of these packages and run the relevant integration tests to ensure no unintended disruptions occur in test utilities.lsp/vscode/package.json (1)
35-38: Updated Dev Dependencies for VSCode Extension
The VSCode extension’s devDependencies have been updated with:
"@types/vscode": "^1.97.0","@volar/language-server": "~2.4.11","@volar/vscode": "~2.4.11", and"esbuild": "^0.25.0".Make sure these changes are verified against the targeted VSCode versions and that the extension builds correctly under different environments.
bundler-packages/config/package.json (1)
69-73: Synchronized Dependency Updates
Within the dependencies section, the following updates have been applied:
"@effect/schema"updated to"0.75.5","@types/node"updated to"^22.13.5","effect"updated to"3.13.2", and"zod"updated to"^3.24.2".These changes mirror improvements seen in other sections of the repository. Please verify that these updates do not adversely affect how configuration is managed across the bundler modules.
experimental/solc/package.json (2)
48-51: Updated Production Dependencies
The production dependencies for the experimental Solc wrapper have been updated as follows:
"@types/resolve"to"^1.20.6","glob"to"^11.0.1","resolve"to"^1.22.10", and"unplugin"to"^2.2.0".Please ensure these updates do not alter any expected runtime behavior in the experimental module.
54-61: Upgraded Dev Dependencies
The devDependencies have seen significant upgrades:
"@types/node": "^22.13.5","abitype": "^1.0.8","solc": "0.8.28","tsup": "^8.4.0","tsx": "^4.19.3","typescript": "^5.7.3","wagmi": "^2.14.12", and"zod": "^3.24.2".Given the breadth of these version bumps, please run comprehensive builds and tests for the experimental Solc workflows to confirm that the integrations remain smooth and that no build-time or runtime discrepancies occur.
bundler-packages/bundler-cache/package.json (2)
69-69: Updated Dependency Version for @types/node.
The dependency version for@types/nodehas been bumped to^22.13.5, which aligns with the coordinated updates across the repository.
72-74: Updated Dev Dependencies Versions.
The updates for@vitest/coverage-v8,@vitest/ui, andtypescriptto^3.0.7,^3.0.7, and^5.7.3respectively ensure consistency and take advantage of the latest fixes and features. Please verify that these upgrades are compatible with your test and build infrastructure.experimental/revm/package.json (1)
62-73: Comprehensive Update of Dev Dependencies.
The updated versions for@vitest/coverage-v8,@vitest/ui,abitype,tsup,typedoc,typedoc-plugin-markdown,typescript,viem,vitest,wagmi,wasm-pack, andzodreflect the latest releases across the toolchain. These updates should improve performance and compatibility; please ensure that no breaking changes affect the WASM build or associated tests.lsp/lsp/package.json (2)
33-37: Updated Core Dependencies for Language Server.
The versions of@volar/language-core,@volar/language-server,@volar/language-service,effect, andsolchave been bumped to~2.4.11,~2.4.11,~2.4.11,3.13.2, and0.8.28respectively. These changes promote consistency and include minor improvements; however, please verify that thesolcupgrade does not inadvertently introduce incompatibilities in Solidity compilation.
47-51: Updated Build Toolchain in Dev Dependencies.
The upgrades fortsup,typedoc,typedoc-plugin-markdown,typescript, andvitestto their latest versions should streamline the build and documentation processes.bundler-packages/resolutions/package.json (2)
68-70: Synchronized Dependency Updates in Resolutions Package.
The update for@types/nodeto^22.13.5, along with bumpingeffectto3.13.2andresolveto^1.22.10, is consistent with the broader dependency refresh across the repository.
73-73: Updated Dev Dependency for OpenZeppelin Contracts.
Raising@openzeppelin/contractsto^5.2.0looks aligned with recent improvements. It would be beneficial to verify that there are no breaking changes in the contract interfaces that might affect dependent modules.bundler-packages/unplugin/package.json (2)
68-71: Latest Versions for Key Dependencies in Unplugin Package.
The dependency updates—effectto3.13.2,solcto0.8.28,unpluginto^2.2.0, andzodto^3.24.2—ensure that the package remains up to date with the repository’s standards. Please verify that these changes work harmoniously in your build and plugin integration workflows.
77-77: Updated Dev Dependency for Type Definitions.
The upgrade of@types/nodeto^22.13.5is in line with other dependency updates. Double-check that node type references throughout the module remain valid.docs/node/package.json (2)
15-20: Review Upgrades for Ethers and Vitest.
The versions for"ethers": "^6.13.5"and"vitest": "^3.0.7"have been incremented. Verify that these new releases do not introduce breaking changes in your codebase.
24-25: Updated React Type Definitions in DevDependencies.
The changes for"@types/react": "^19.0.10"and"@types/react-dom": "^19.0.4"ensure compatibility with React 19. Double-check that these updates are consistent with the usage across the project.bundler-packages/compiler/package.json (2)
69-71: Confirm Compatibility of Upgraded Core Dependencies.
The updates for"@types/node": "^22.13.5","effect": "3.13.2", and"resolve": "^1.22.10"appear aligned with the overall dependency bump strategy. Please verify that these upgrades do not introduce any runtime or compilation issues, especially considering any breaking changes ineffect.
75-79: Validate Critical Blockchain-Related Library Upgrades.
Upgrading"@openzeppelin/contracts"to"5.2.0"and"solc"to"0.8.28"can be significant for your smart contract workflows. Ensure that your contracts compile correctly and that any changes in these libraries are properly accounted for in your testing and deployment processes.docs/bundler/package.json (2)
12-14: Updated Dependencies for React and VOCS.
The dependency versions for"react": "^19.0.0","react-dom": "^19.0.0", and"vocs": "1.0.0-alpha.62"have been set explicitly. Please check that these versions are aligned with your project’s overall tooling strategy and that any breaking changes in VOCS are managed.
17-18: Ensure Dev Tooling Compatibility with Upgraded TypeScript.
The changes in the devDependencies ("@types/react": "^19.0.10"and"typescript": "^5.7.3") promote a modern development setup. Verify again that there are no emerging type conflicts or configuration issues in your build scripts.experimental/viem-effect/package.json (1)
132-147: Review DevDependency Upgrades for Build and Testing Systems.
The updated Babel packages,tsup,typescript, as well as testing libraries like"@vitest/coverage-v8","@vitest/ui", and"vitest"have undergone version bumps. Confirm that your build process, linting, and testing pipelines are adjusted to work seamlessly with these new versions. Adjust configuration files if necessary.examples/esbuild/package.json (3)
19-20: Verify Consistency of Upgraded Core Dependencies in Examples.
Upgrading"viem"to"^2.23.5"and"zod"to"^3.24.2"aligns with the other modules in the monorepo. Please test that these updates do not negatively affect example applications, especially any contract interactions or schema validations.
23-24: Updated Blockchain and Testing Dependencies in DevDependencies.
The bumps for"@nomicfoundation/hardhat-foundry"and"@openzeppelin/contracts"ensure up-to-date blockchain tooling. Validate that these updated versions work with your hardhat configurations and test suites.
30-36: Ensure DevEnvironment Compatibility with Major Tooling Upgrades.
The updates in devDependencies—for"@types/node","esbuild","solc","tsx", and"typescript"—provide a more modern development environment. Make sure that your build process, as well as compilation and type-checking procedures, continue to work without issues.package.json (1)
45-67: Dependency Version Bump for DevDependencies
All devDependency versions have been updated to their latest releases. These updates include important tools (e.g., TypeScript, Vitest, tsup) and libraries that may affect build and test processes. Please ensure that none of these upgrades introduce inadvertent breaking changes by running the full test suite and verifying build scripts.examples/vite/package.json (2)
28-48: Upgrade of Project Dependencies in "dependencies"
The dependency versions (e.g., @rainbow-me/rainbowkit, @tanstack/react-query, ethers, react/react-dom, uuid, viem, etc.) have been bumped up to their latest releases. This update helps maintain consistency across the project. Please confirm that these version updates do not adversely affect runtime behavior or integration with external services.
51-69: Upgrade of Dev Tooling in "devDependencies"
DevDependency updates—covering libraries such as @openzeppelin/contracts, @testing-library/react, solc, typescript, vite, and vitest—are in line with the overall dependency refresh. Ensure that build, lint, and test scripts run smoothly with these newer versions.examples/svelte-ethers/package.json (2)
16-19: Upgrade of the "ethers" Dependency
The version of the ethers library has been updated to ^6.13.5. Verify that integration with any blockchain contract interfaces or related logic remains fully compatible after the upgrade.
20-32: Upgrade of DevDependencies for Svelte-Ethers Example
DevDependencies (including @openzeppelin/contracts, @sveltejs/adapter-auto, @sveltejs/kit, solc, svelte, svelte-check, typescript, vite, vite-plugin-top-level-await, and vitest) have been updated. Double-check that these changes do not introduce integration issues in the Svelte environment and that development processes (e.g., type-checking, testing) continue to work as expected.cli/package.json (2)
59-82: CLI Dependencies Update
The dependencies for the CLI package have been updated (notably, @tanstack/react-query, fs-extra, ink, react, tsup, zod, and zustand). These modernized versions should enhance stability and performance, but please run the CLI commands to ensure that none of the breaking changes from these upgrades affect functionality.
88-95: CLI DevDependencies Upgrade
The upgrades for devDependencies (including @types/react, @vitest/coverage-v8, @vitest/ui, chalk, typescript, and vitest) are consistent with the project-wide refresh. It is advisable to verify that the test coverage and typechecking processes remain intact after these updates.examples/next/package.json (2)
20-52: Update of Dependencies in Next.js Example
A broad set of dependencies—including various @radix-ui components, @shazow/whatsabi, @tanstack/react-table, class-variance-authority, cmdk, lucide-react, next, next-themes, react, react-dom, react-use, sonner, tailwind-merge, vaul, viem, web-streams-polyfill, and zustand—have been updated to newer versions. These changes should ensure modern UI behavior and feature compatibility. Please test the UI components and Next.js build process for any unforeseen issues.
55-64: Update of DevDependencies for Next.js Example
DevDependencies such as @ianvs/prettier-plugin-sort-imports, @types/node, @types/react, @types/react-dom, postcss, prettier, prettier-plugin-tailwindcss, tailwindcss, and typescript have been updated. These changes are expected to improve code formatting, linting, and type checking. Run the development and build scripts to ensure everything remains consistent.
roninjin10
force-pushed
the
02-27-_arrow_up_chore_pnpm_up_--latest
branch
from
e5021ab to
97de6dc
Compare
Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information
Your ENS/address:
Summary by CodeRabbit