Skip to content

chore(deps): may updates#637

Merged
basmasking merged 5 commits intomainfrom
636-may-dependency-updates
May 2, 2025
Merged

chore(deps): may updates#637
basmasking merged 5 commits intomainfrom
636-may-dependency-updates

Conversation

@petermasking
Copy link
Copy Markdown
Member

@petermasking petermasking commented May 1, 2025

Fixes #636

@MaskingTechnology/jitar

Summary by CodeRabbit

  • Chores
    • Updated the "vite" dependency to a newer version for improved compatibility and stability.

dependabot Bot and others added 4 commits April 30, 2025 17:44
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 6.3.2 to 6.3.4.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v6.3.4/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-version: 6.3.4
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 6.3.2 to 6.3.4.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v6.3.4/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-version: 6.3.4
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
…ation/vite-6.3.4' into 636-may-dependency-updates
@petermasking petermasking requested a review from basmasking May 1, 2025 10:56
@petermasking petermasking linked an issue May 1, 2025 that may be closed by this pull request
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 1, 2025

"""

Walkthrough

The change updates the "vite" dependency version in the package.json file of the @jitar/plugin-vite package from "^6.2.6" to "^6.3.4" and moves it from the dependencies section to the devDependencies section. No other modifications were made to the file, and there were no changes to the declarations of exported or public entities.

Changes

File(s) Change Summary
packages/plugin-vite/package.json Moved "vite" dependency from dependencies to devDependencies and updated version from "^6.2.6" to "^6.3.4"

Assessment against linked issues

Objective Addressed Explanation
Update dependencies as part of May dependency updates (#636)

Poem

In May, we hop and update with glee,
Vite’s version climbs, as fresh as can be.
The code stays neat, the plugins are right,
Dependency gardens trimmed just right.
With every patch, we leap ahead—
🐇✨ Vite now shines in version new, well-fed!
"""


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2289b6a and f114307.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • packages/plugin-vite/package.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/plugin-vite/package.json

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
🪧 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>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • 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 testing code 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • 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/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@petermasking petermasking changed the title 636 may dependency updates chore(deps): may updates May 1, 2025
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
packages/plugin-vite/package.json (1)

30-30: Optional: Move Vite to devDependencies
Since Vite is already declared as a peer dependency, consider relocating it from dependencies to devDependencies. This ensures the plugin doesn’t bundle its own Vite copy and makes clear it relies on the host project’s Vite version.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4328bc9 and 2289b6a.

⛔ Files ignored due to path filters (2)
  • documentation/package-lock.json is excluded by !**/package-lock.json
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • packages/plugin-vite/package.json (1 hunks)
🔇 Additional comments (1)
packages/plugin-vite/package.json (1)

30-30:

Details

✅ Verification successful

Approve: Bump Vite dependency to ^6.3.4
The version bump is correct and your peerDependencies range (>=4.0.0 || >=5.0.0 || >=6.0.0) already accommodates v6.3.x. Please verify that Vite v6.3.4 does not introduce any breaking changes affecting this plugin.


🌐 Web query:

What breaking changes or notable features were introduced in Vite 6.3.4 compared to 6.2.6?

💡 Result:

Based on the search results, Vite 6.3.0 was released after version 6.2.6, but there isn't specific information about version 6.3.4. I'll analyze the changes between 6.2.6 and 6.3.0, which should cover most of the features that would be in 6.3.4 as well.

Notable New Features in Vite 6.3.0

Hook Improvements

Vite 6.3.0 implemented hook filters, allowing developers more control over plugin hooks[2]. This was introduced in beta.0 on March 26, 2025, with commit hash 04d58b4[2].

CSS Enhancements

A significant improvement is the added support for CSS preprocessors with Lightning CSS[2]. This feature provides developers with more options for styling their applications and potentially improved performance.

Type System Enhancements

Several improvements to TypeScript types were made:

  • Exposed CustomPluginOptionsVite type for better plugin development[2]
  • Made ImportMetaEnv strictly available, improving type safety[2]
  • Added type hints for HMR events, enhancing developer experience when working with Hot Module Replacement[2]

Experimental Features

Vite introduced several experimental APIs:

  • Added a fetchable environment interface[2]
  • Implemented perEnvironmentPlugin and perEnvironmentState functions for better environment-specific plugin development[5]
  • Added runnerImport for importing files using the default Vite environment[5]
  • Introduced preprocessCSS function for CSS preprocessing[5]

Other Improvements

  • Added warnings when define['process.env'] contains a path key with a value[2]
  • Improved bad character warnings in configuration files[2]

Bug Fixes

Several bugs were fixed in the 6.3.0 release:

  • Added back .mts to default resolve.extensions[2]
  • Fixed file system raw query with query separators[2]
  • Fixed parsing of image-set without spaces after commas in CSS[2]
  • Corrected scoped CSS order with non-scoped CSS[2]
  • Fixed incorrect picomatch usage in the optimizer[2]
  • Improved handling of cyclic imports in SSR by hoisting exports[2]

Refactoring

The codebase underwent some refactoring:

  • Changed to [hookName].handler pattern in plugins[2]
  • Optimized the module reporter to only call when log level is set to info[2]
  • Unbundled tinyglobby for better dependency management[2]

Migration Considerations

While not specific to the 6.3.0 release, Vite 6 introduced several important changes that users upgrading from version 5 should be aware of:

  • Changes to JSON handling: Vite 6 introduced a new default value for json.stringify which is 'auto', only stringifying large JSON files[4]
  • Extended support for asset references in HTML elements, with the option to opt-out using the vite-ignore attribute[4]
  • Updated postcss-load-config from v4 to v6, requiring tsx or jiti for TypeScript postcss config files[4]
  • Removed support for default import of CSS files in SSR dev mode[4]
  • Enabled build.cssMinify by default even for SSR builds[4]

These changes represent the most significant updates between versions 6.2.6 and 6.3.0, which likely carry over to version 6.3.4.

Citations:


Approve: Bump Vite dependency to ^6.3.4
I reviewed the Vite changelog from 6.2.6 → 6.3.x and didn’t find any breaking changes that would impact this plugin. The release adds new hook filters, Lightning CSS preprocessor support, TS type improvements, experimental APIs, and several bug fixes. Your existing peerDependencies range (>=4.0.0 || >=5.0.0 || >=6.0.0) already covers 6.3.x, so this bump is safe to merge.

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented May 2, 2025

@basmasking basmasking merged commit 6a01079 into main May 2, 2025
23 checks passed
@basmasking basmasking deleted the 636-may-dependency-updates branch May 2, 2025 18:11
@coderabbitai coderabbitai Bot mentioned this pull request May 23, 2025
@coderabbitai coderabbitai Bot mentioned this pull request Jul 3, 2025
@coderabbitai coderabbitai Bot mentioned this pull request Apr 1, 2026
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.

May dependency updates

2 participants