fix: bump dev dependencies to latest

[aversini]

Summary by CodeRabbit

• Chores
  • Updated dependencies for better performance and stability.
  • Specified the package manager version to ensure consistent environment setup.

[phylum-io]

Phylum OSS Supply Chain Risk Analysis - INCOMPLETE

The analysis contains 5 package(s) Phylum has not yet processed,
preventing a complete risk analysis. Phylum is processing these
packages currently and should complete soon.
Please wait for up to 30 minutes, then re-run the analysis.

View this project in the Phylum UI

[coderabbitai]

Walkthrough

The recent update involves incrementing versions of specific development dependencies and adjusting the package management configuration. Additionally, within a specific package, dependencies now reference local workspace paths, enhancing project cohesion and dependency management. This change streamlines development processes and ensures consistency across the project's components.

Changes

File(s)	Change Summary
package.json	Updated @versini/dev-dependencies-client to 4.1.15, @versini/dev-dependencies-types to 1.1.6, and specified packageManager as [email protected] with a SHA-256 checksum.
packages/.../bundlesize/package.json	Updated dependencies @versini/ui-components and @versini/ui-hooks to use workspace paths.

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[github-actions]

Bundle Size

Status	File	Size (Gzip)	Limits
✅	style.css	7.29 KB	8 KB
✅	index.js	19.36 KB	20 KB
✅	vendor.js	65.07 KB	67 KB

Overall bundle size: 91.71 KB
Overall status: ✅

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between fda49e6 and 80c7212.

Files selected for processing (3)

• package.json (1 hunks)
• packages/bundlesize/package.json (1 hunks)
• pnpm-lock.yaml (85 hunks)

Files not summarized due to errors (1)

• pnpm-lock.yaml: Error: Message exceeds token limit

Additional comments: 20

packages/bundlesize/package.json (1)

• 16-17: The update to use workspace paths for @versini/ui-components and @versini/ui-hooks is a good practice in monorepos. It ensures that local, workspace-specific versions of these packages are used, which can aid in testing and integration processes.

package.json (2)

• 17-18: Updating the versions of @versini/dev-dependencies-client and @versini/dev-dependencies-types ensures that the project benefits from the latest updates, including new features and bug fixes.
• 21-21: Specifying the packageManager field with "[email protected]" and a precise SHA-256 checksum is a commendable practice. It standardizes the package management process across different development environments, potentially reducing issues related to package installation and versioning.

pnpm-lock.yaml (17)

• 15-19: The update of @versini/dev-dependencies-client and @versini/dev-dependencies-types to newer versions is noted. Ensure that these updates do not introduce breaking changes that could affect the project's build or runtime behavior.
• 27-30: Refactoring dependencies @versini/ui-components and @versini/ui-hooks to use workspace paths instead of wildcard versions is a good practice for managing internal dependencies. This ensures that the local, workspace-specific versions of these packages are used, which can aid in testing and integration processes.
• 593-603: The change from dev: false to dev: true for the /@eslint-community/[email protected] package indicates a shift in how this dependency is categorized. This should be intentional and aligned with the package's actual usage within the project. If this package is only used during development and not required in production builds, this change is appropriate.
• 712-712: The addition of @types/node version 20.11.17 to a dependency list. It's important to ensure that this version is compatible with the project's current Node.js runtime environment and does not introduce type definitions that conflict with the project's codebase.
• 768-768: Updating @types/node to version 20.11.20 suggests an effort to keep type definitions up-to-date. Verify that all Node.js API usages in the project are compatible with this version to avoid type-related issues.
• 924-924: The addition of semver version 7.6.0 across multiple dependencies indicates a widespread update or addition of this package. Given semver's role in versioning, ensure that its usage across the project is consistent and that this version meets the project's needs.
• 1465-1465: The addition of rollup version 4.12.0 as a dependency in a package. This version should be compatible with the project's build configuration and plugins. It's crucial to test the build process thoroughly after such updates to catch any incompatibilities.
• 2224-2224: The addition of @types/node version 20.11.17 in the /@types/[email protected] package. Consistency in Node.js type definitions across the project is important to avoid conflicts. Ensure that this version aligns with the project's overall dependency management strategy.
• 2344-2366: The update to @typescript-eslint/eslint-plugin and related packages to version 7.0.2 involves several dependencies and configurations. It's important to ensure that these updates are compatible with the project's existing ESLint configuration and TypeScript version. Additionally, verify that no new linting errors or warnings are introduced by this update.
• 2480-2512: The update to @versini/[email protected] includes a significant number of dependencies. This change should be carefully reviewed to ensure that it does not introduce any version conflicts or breakages in the project's build or runtime behavior. It's also important to verify that all the added dependencies are necessary and used within the project.
• 2560-2560: The update to @versini/[email protected] includes changes to several dependencies. Ensure that these updates are compatible with the project's configuration and do not introduce any issues. It's particularly important to verify the updates to ESLint plugins and TypeScript-related packages, as they can have a significant impact on code quality and build processes.
• 2585-2596: The update to @versini/[email protected] includes updates to type definitions. Ensure that these updates are compatible with the project's TypeScript version and do not introduce any type errors or warnings. It's also important to verify that the updated type definitions accurately reflect the APIs they describe.
• 2613-2613: The update to @vitejs/[email protected] includes a dependency on vite version 5.1.4. Ensure that this version of Vite is compatible with the project's build configuration and does not introduce any build or runtime issues.
• 2640-2641: The update to @vitest/[email protected] includes a dependency on vitest version 1.3.1. Verify that this version of Vitest works correctly with the project's test configuration and does not introduce any issues with test execution or coverage reporting.
• 9293-9312: The update to [email protected] and the addition of various @rollup/rollup-* packages as optional dependencies. This change suggests a significant update to the project's build system. Ensure that the updated Rollup version and the added packages are compatible with the project's build configuration and do not introduce any build issues.
• 10639-10648: The addition of [email protected] with a dependency on vite version 5.1.4. This suggests an update or addition related to server-side rendering or testing configurations. Ensure that this package and its Vite dependency are correctly integrated into the project and do not introduce any runtime or build issues.
• 10668-10694: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [10660-10676]

The update to [email protected] includes dependencies on [email protected], [email protected], and [email protected]. This change impacts the project's type declaration generation. Ensure that the updated plugin and its dependencies are compatible with the project's TypeScript and build configurations, and verify that type declarations are correctly generated without issues.