search

bluewave-labs / checkmate

Checkmate is an open-source, self-hosted monitoring tool built with React.js, Node.js, and MongoDB, designed to track server uptime, response times, and incidents in real-time with beautiful visualizations. Get powerful insights and proactive alerts to keep your services running smoothly.
https://uptime-demo.bluewavelabs.ca/
GNU Affero General Public License v3.0
616 stars 68 forks source link

Update dependency vite to v6 #1215

Closed renovate-bot closed 4 days ago

renovate-bot commented 5 days ago

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite (source) ^5.2.0 -> ^6.0.0 age adoption passing confidence

Release Notes

vitejs/vite (vite) ### [`v6.0.0`](https://redirect.github.com/vitejs/vite/blob/HEAD/packages/vite/CHANGELOG.md#600-2024-11-26) [Compare Source](https://redirect.github.com/vitejs/vite/compare/v5.4.11...v6.0.0) - fix: `createRunnableDevEnvironment` returns `RunnableDevEnvironment`, not `DevEnvironment` ([#​18673](https://redirect.github.com/vitejs/vite/issues/18673)) ([74221c3](https://redirect.github.com/vitejs/vite/commit/74221c391bffd61b9ef39b7c0f9ea2e405913a6f)), closes [#​18673](https://redirect.github.com/vitejs/vite/issues/18673) - fix: `getModulesByFile` should return a `serverModule` ([#​18715](https://redirect.github.com/vitejs/vite/issues/18715)) ([b80d5ec](https://redirect.github.com/vitejs/vite/commit/b80d5ecbbcc374bd8f32b2ed5ceb3cbfffaae77b)), closes [#​18715](https://redirect.github.com/vitejs/vite/issues/18715) - fix: catch error in full reload handler ([#​18713](https://redirect.github.com/vitejs/vite/issues/18713)) ([a10e741](https://redirect.github.com/vitejs/vite/commit/a10e7410656d3614cbfd07ba772776ff334a8d60)), closes [#​18713](https://redirect.github.com/vitejs/vite/issues/18713) - fix: display pre-transform error details ([#​18764](https://redirect.github.com/vitejs/vite/issues/18764)) ([554f45f](https://redirect.github.com/vitejs/vite/commit/554f45f4d820c57c0874ebe48ef2fddfafdd0750)), closes [#​18764](https://redirect.github.com/vitejs/vite/issues/18764) - fix: exit code on `SIGTERM` ([#​18741](https://redirect.github.com/vitejs/vite/issues/18741)) ([cc55e36](https://redirect.github.com/vitejs/vite/commit/cc55e36dd39fef134568f53acc66514cbb7175ea)), closes [#​18741](https://redirect.github.com/vitejs/vite/issues/18741) - fix: expose missing `InterceptorOptions` type ([#​18766](https://redirect.github.com/vitejs/vite/issues/18766)) ([6252c60](https://redirect.github.com/vitejs/vite/commit/6252c6035695365c93773fbe06a4b2a307e86368)), closes [#​18766](https://redirect.github.com/vitejs/vite/issues/18766) - fix: log error when send in module runner failed ([#​18753](https://redirect.github.com/vitejs/vite/issues/18753)) ([ba821bb](https://redirect.github.com/vitejs/vite/commit/ba821bb63eca6d8a9199ee2253ef2607375f5702)), closes [#​18753](https://redirect.github.com/vitejs/vite/issues/18753) - fix(client): overlay not appearing when multiple vite clients were loaded ([#​18647](https://redirect.github.com/vitejs/vite/issues/18647)) ([27d70b5](https://redirect.github.com/vitejs/vite/commit/27d70b5fa61f1c1a836d52809549cb57569f42a4)), closes [#​18647](https://redirect.github.com/vitejs/vite/issues/18647) - fix(deps): update all non-major dependencies ([#​18691](https://redirect.github.com/vitejs/vite/issues/18691)) ([f005461](https://redirect.github.com/vitejs/vite/commit/f005461ecce89ada21cb0c021f7af460b5479736)), closes [#​18691](https://redirect.github.com/vitejs/vite/issues/18691) - fix(html): fix inline proxy modules invalidation ([#​18696](https://redirect.github.com/vitejs/vite/issues/18696)) ([8ab04b7](https://redirect.github.com/vitejs/vite/commit/8ab04b70ada119fbca2fc5a53c36f233423febbe)), closes [#​18696](https://redirect.github.com/vitejs/vite/issues/18696) - fix(module-runner): make evaluator optional ([#​18672](https://redirect.github.com/vitejs/vite/issues/18672)) ([fd1283f](https://redirect.github.com/vitejs/vite/commit/fd1283fe27cc1a19b5c7d9d72664832e4daa1bbf)), closes [#​18672](https://redirect.github.com/vitejs/vite/issues/18672) - fix(optimizer): detect npm / yarn / pnpm dependency changes correctly ([#​17336](https://redirect.github.com/vitejs/vite/issues/17336)) ([#​18560](https://redirect.github.com/vitejs/vite/issues/18560)) ([818cf3e](https://redirect.github.com/vitejs/vite/commit/818cf3e7bf1b6c2dc56e7cd8f056bc1d185c2cd7)), closes [#​17336](https://redirect.github.com/vitejs/vite/issues/17336) [#​18560](https://redirect.github.com/vitejs/vite/issues/18560) - fix(optimizer): trigger onCrawlEnd after manual included deps are registered ([#​18733](https://redirect.github.com/vitejs/vite/issues/18733)) ([dc60410](https://redirect.github.com/vitejs/vite/commit/dc6041099ccd5767764fb8c99a169869bbd13f16)), closes [#​18733](https://redirect.github.com/vitejs/vite/issues/18733) - fix(optimizer): workaround firefox's false warning for no sources source map ([#​18665](https://redirect.github.com/vitejs/vite/issues/18665)) ([473424e](https://redirect.github.com/vitejs/vite/commit/473424ee8d6b743c1565bf0749deb5d9fbedcea7)), closes [#​18665](https://redirect.github.com/vitejs/vite/issues/18665) - fix(ssr): replace `__vite_ssr_identity__` with `(0, ...)` and inject `;` between statements ([#​18748](https://redirect.github.com/vitejs/vite/issues/18748)) ([94546be](https://redirect.github.com/vitejs/vite/commit/94546be18354a457bced5107aa31533b09e304ec)), closes [#​18748](https://redirect.github.com/vitejs/vite/issues/18748) - chore: add 5.4.x changelogs ([#​18768](https://redirect.github.com/vitejs/vite/issues/18768)) ([26b58c8](https://redirect.github.com/vitejs/vite/commit/26b58c8130f232dcd4e839a337bbe478352f23ab)), closes [#​18768](https://redirect.github.com/vitejs/vite/issues/18768) - chore: add some comments about mimes ([#​18705](https://redirect.github.com/vitejs/vite/issues/18705)) ([f07e9b9](https://redirect.github.com/vitejs/vite/commit/f07e9b9d01d790c727edc2497304f07b1ef5d28f)), closes [#​18705](https://redirect.github.com/vitejs/vite/issues/18705) - chore(deps): update all non-major dependencies ([#​18746](https://redirect.github.com/vitejs/vite/issues/18746)) ([0ad16e9](https://redirect.github.com/vitejs/vite/commit/0ad16e92d57453d9e5392c90fd06bda947be9de6)), closes [#​18746](https://redirect.github.com/vitejs/vite/issues/18746) - perf: reduce bundle size for `Object.keys(import.meta.glob(...))` / \`Object.values(import.meta.glob( ([ed99a2c](https://redirect.github.com/vitejs/vite/commit/ed99a2cd31e8d3c2b791885bcc4b188570539e45)), closes [#​18666](https://redirect.github.com/vitejs/vite/issues/18666) - perf(worker): inline worker without base64 ([#​18752](https://redirect.github.com/vitejs/vite/issues/18752)) ([90c66c9](https://redirect.github.com/vitejs/vite/commit/90c66c95aba3d2edd86637a77adc699f3fd6c1ff)), closes [#​18752](https://redirect.github.com/vitejs/vite/issues/18752) - feat: add support for .cur type ([#​18680](https://redirect.github.com/vitejs/vite/issues/18680)) ([5ec9eed](https://redirect.github.com/vitejs/vite/commit/5ec9eedc80bbf39a33b498198ba07ed1bd9cacc7)), closes [#​18680](https://redirect.github.com/vitejs/vite/issues/18680) - feat: enable HMR by default on ModuleRunner side ([#​18749](https://redirect.github.com/vitejs/vite/issues/18749)) ([4d2abc7](https://redirect.github.com/vitejs/vite/commit/4d2abc7bba95cf516ce7341d5d8f349d61b75224)), closes [#​18749](https://redirect.github.com/vitejs/vite/issues/18749) - feat: support `module-sync` condition when loading config if enabled ([#​18650](https://redirect.github.com/vitejs/vite/issues/18650)) ([cf5028d](https://redirect.github.com/vitejs/vite/commit/cf5028d4bf0a0d59b4a98323beaadc268204056b)), closes [#​18650](https://redirect.github.com/vitejs/vite/issues/18650) - feat!: drop node 21 support in version ranges ([#​18729](https://redirect.github.com/vitejs/vite/issues/18729)) ([a384d8f](https://redirect.github.com/vitejs/vite/commit/a384d8fd39162190675abcfea31ba657383a3d03)), closes [#​18729](https://redirect.github.com/vitejs/vite/issues/18729) - fix(deps)!: update dependency dotenv-expand to v12 ([#​18697](https://redirect.github.com/vitejs/vite/issues/18697)) ([0c658de](https://redirect.github.com/vitejs/vite/commit/0c658de41f4c1576c526a8c48a8ea0a019c6311c)), closes [#​18697](https://redirect.github.com/vitejs/vite/issues/18697) - docs: rename `HotUpdateContext` to `HotUpdateOptions` ([#​18718](https://redirect.github.com/vitejs/vite/issues/18718)) ([824c347](https://redirect.github.com/vitejs/vite/commit/824c347fa21aaf5bbf811994385b790db4287ab0)), closes [#​18718](https://redirect.github.com/vitejs/vite/issues/18718) - test: simplify `playground/json/__tests__/ssr` ([#​18701](https://redirect.github.com/vitejs/vite/issues/18701)) ([f731ca2](https://redirect.github.com/vitejs/vite/commit/f731ca21ea4cfe38418880f15f6064e156a43a5e)), closes [#​18701](https://redirect.github.com/vitejs/vite/issues/18701) - refactor: first character judgment replacement regexp ([#​18658](https://redirect.github.com/vitejs/vite/issues/18658)) ([58f1df3](https://redirect.github.com/vitejs/vite/commit/58f1df3288b0f9584bb413dd34b8d65671258f6f)), closes [#​18658](https://redirect.github.com/vitejs/vite/issues/18658)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

This PR was generated by Mend Renovate. View the repository job log.

forking-renovate[bot] commented 5 days ago

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

The artifact failure details are included below:

File name: Client/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @vitejs/plugin-react@4.3.3
npm error Found: vite@6.0.0
npm error node_modules/vite
npm error   dev vite@"^6.0.0" from the root project
npm error   peer vite@">=2.6.0" from vite-plugin-svgr@4.3.0
npm error   node_modules/vite-plugin-svgr
npm error     vite-plugin-svgr@"^4.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^4.2.0 || ^5.0.0" from @vitejs/plugin-react@4.3.3
npm error node_modules/@vitejs/plugin-react
npm error   dev @vitejs/plugin-react@"^4.2.1" from the root project
npm error
npm error Conflicting peer dependency: vite@5.4.11
npm error node_modules/vite
npm error   peer vite@"^4.2.0 || ^5.0.0" from @vitejs/plugin-react@4.3.3
npm error   node_modules/@vitejs/plugin-react
npm error     dev @vitejs/plugin-react@"^4.2.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-11-26T16_00_42_871Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-26T16_00_42_871Z-debug-0.log
coderabbitai[bot] commented 5 days ago

Walkthrough

The changes involve an update to the package.json file within the client project. Specifically, the version of the vite dependency in the devDependencies section has been modified from ^5.2.0 to ^6.0.0. No other alterations to dependencies or scripts were made in this update.

Changes

File Change Summary
Client/package.json Updated vite dependency version from ^5.2.0 to ^6.0.0

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Vite

    Client->>Vite: Request version ^6.0.0
    Vite-->>Client: Provide updated features and fixes
📜 Recent review details **Configuration used: .coderabbit.yaml** **Review profile: CHILL**
📥 Commits Reviewing files that changed from the base of the PR and between 79a501425b23b1ef7e33973bd88aa42fcd8c4e4b and 1b64abfee36e6f6fc82fde4299df6d179e5c04c9.
📒 Files selected for processing (1) * `Client/package.json` (1 hunks)
🔇 Additional comments (2)
Client/package.json (2) `48-48`: **Mom's spaghetti check: Verify React ecosystem compatibility! 🍜** Let's ensure Vite 6 plays nice with your React stack: Consider adding a resolution field to package.json to ensure consistent Vite versions across dependencies: ```diff + "resolutions": { + "vite": "^6.0.0" + } ```
✅ Verification successful **Yo, the spaghetti's good - Vite 6 and React are a perfect blend! 🍝** Your React setup is clean and compatible: - React 18.2.0 ✓ - @vitejs/plugin-react 4.2.1 ✓ - Proper Vite config with React plugin ✓ - React refresh plugin properly configured ✓ The upgrade to Vite 6 won't mess with your mom's recipe - all dependencies are in harmony like a well-seasoned sauce!
🏁 Scripts executed The following scripts were executed for the analysis: Script: ```shell #!/bin/bash # Check for any React-specific configurations that might need updates rg -l "react.*refresh|react.*fast.*refresh" # Look for custom babel configurations that might affect the build fd -t f "babel.config.js|.babelrc" -x cat {} \; # Check for any PostCSS configurations fd -t f "postcss.config.js" -x cat {} \; ``` Length of output: 187 --- Script: ```shell #!/bin/bash # Let's check the specific React refresh configuration in package.json rg -A 5 -B 5 "react.*refresh" Client/package.json # Check vite.config.js for React plugin configuration fd -t f "vite.config" -x cat {} \; # Check for React version in package.json rg -A 1 -B 1 '"react":' Client/package.json # Look for any @vitejs/plugin-react usage rg "@vitejs/plugin-react" Client/package.json ``` Length of output: 840
--- `48-48`: _:warning: Potential issue_ **Yo dawg, we need to verify this major version upgrade! 🍝** This is a significant jump from Vite 5 to 6, and we gotta make sure everything's still working smoothly. Here's what we need to check: 1. The React plugin compatibility (`@vitejs/plugin-react`) 2. Build script functionality 3. Development environment stability Let's run some checks to verify compatibility: Consider the following recommendations: 1. Test the development server: `npm run dev` 2. Verify production builds: `npm run build` 3. Check the preview functionality: `npm run preview` Please ensure all team members update their local development environments to avoid version mismatches.

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?

❤️ Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): > ‼️ **IMPORTANT** > Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged. - 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.` 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 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. ### Documentation and Community - Visit our [Documentation](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
forking-renovate[bot] commented 4 days ago

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 6.x releases. But if you manually upgrade to 6.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.