Skip to content

chore: update npm dependencies#28

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm
Open

chore: update npm dependencies#28
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm

Conversation

@renovate
Copy link

@renovate renovate bot commented Jul 4, 2023

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
@vitest/coverage-c8 (source) ^0.28.5^0.33.0 age confidence devDependencies minor
eslint (source) ^8.57.1^9.39.2 age confidence devDependencies major
eslint-config-reearth ^0.2.1^0.3.8 age confidence devDependencies minor
node (source) >=12>=24.13.0 age confidence engines major
prettier (source) ^2.8.8^3.8.1 age confidence devDependencies major
typescript (source) ^5.7.2^5.9.3 age confidence devDependencies patch
vite (source) ^6.0.3^7.3.1 age confidence devDependencies major
vite-plugin-dts ^4.3.0^4.5.4 age confidence devDependencies patch
vitest (source) ^0.28.5^4.0.18 age confidence devDependencies major

Release Notes

vitest-dev/vitest (@​vitest/coverage-c8)

v0.33.0

Compare Source

   🚨 Breaking Changes
  • Revert default include patterns  -  by @​so1ve #​3729
    • 0.32.0 changed the default include globs to be compatible with Jest. After a discussion with the community, we are reverting this change because it turned out to be non-intuitive.
   🐞 Bug Fixes
    View changes on GitHub

v0.32.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.32.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.32.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.32.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.32.0

Compare Source

   🚨 Breaking Changes
  • Throw an error, if the module cannot be resolved  -  by @​sheremet-va in #​3307 (1ad63)
    • Vitest used to fall back to the original import when it could not resolve it to the file path or the virtual module. This leads to hard-to-find module graph mismatches if you had incorrect alias or relied on relative imports to be resolved to the project root (which is usual behavior in TypeScript) because the code accidentally "worked". With this release, Vitest will now throw an error if it cannot resolve the module - there are possible edge cases that are not covered yet, so if you have any problems with this, please open a separate issue with reproduction.
  • Improve globs  -  by @​nickmccurdy in #​3392 (19ecc)
    • Vitest now has glob patterns similar to Jest for better compatibility. It's possible that some files will be considered test files when previously they were not. For example, Vitest now considers test.js to be a test file. Also any file in __tests__ is now considered to be a test, not just files with test or spec suffix.
  • Add @vitest/coverage-v8 package  -  by @​AriPerkkio in #​3339 (82112)
    • Vitest now uses v8 code coverage directly for better performance. @vitest/coverage-c8 is deprecated as Vitest no longer uses c8 package for coverage output. It will not be updated anymore, and Vitest will fail in the next version if the user has c8 as their coverage provider. Please, install the new @vitest/coverage-v8 package if you previously used @vitest/coverage-c8.
  • mocker: Don't restore mock to the original if the module is automocked  -  by @​sheremet-va in #​3518 (c1004)
    • spy.mockRestore on auto-mocked named exports will no longer restore their implementation to the actual function. This behavior better matches what Jest does.
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.0

Compare Source

   🚨 Breaking Changes
  • Remove browser from allowed pools inside poolMatchGlob config option. Please, use Vitest workspaces for running tests in the browser.

  • Move assertion declarations to expect package  -  by @​sheremet-va in #​3294 (cf3af)

    • The change should be minor:
    - declare namespace Vi {
    + declare module 'vitest' {
       interface Assertion<T = any> extends CustomMatchers<T> {}
       interface AsymmetricMatchersContaining extends CustomMatchers {}
    }
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.30.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.30.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.29.8

Compare Source

   🚀 Features
   🐞 Bug Fixes

Configuration

📅 Schedule: Branch creation - "before 3:00 am on the 4th day of the month" (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

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

@renovate renovate bot requested a review from rot1024 as a code owner July 4, 2023 02:38
@renovate renovate bot force-pushed the renovate/npm branch 4 times, most recently from 3e9859f to 8ed296d Compare July 12, 2023 05:26
@renovate renovate bot force-pushed the renovate/npm branch 5 times, most recently from ebd0125 to d234e0c Compare July 21, 2023 02:31
@renovate renovate bot force-pushed the renovate/npm branch 3 times, most recently from d1f3203 to 84bea88 Compare July 29, 2023 02:16
@renovate renovate bot force-pushed the renovate/npm branch 4 times, most recently from 22192d4 to dbdc59e Compare August 5, 2023 05:59
@renovate renovate bot force-pushed the renovate/npm branch 3 times, most recently from 42044b6 to 5213d5a Compare August 12, 2023 08:03
@renovate renovate bot force-pushed the renovate/npm branch 2 times, most recently from acd9ada to ddaf390 Compare August 18, 2023 14:42
@renovate renovate bot force-pushed the renovate/npm branch 2 times, most recently from 39f62ac to a5fe96a Compare August 30, 2023 08:45
@renovate renovate bot force-pushed the renovate/npm branch 4 times, most recently from 534867a to 087f5da Compare September 23, 2023 08:36
@renovate renovate bot force-pushed the renovate/npm branch 3 times, most recently from cb80f4c to 457a34f Compare November 18, 2023 08:28
@renovate renovate bot force-pushed the renovate/npm branch 2 times, most recently from ab3b2aa to c0e7095 Compare November 23, 2023 08:10
@renovate renovate bot force-pushed the renovate/npm branch 4 times, most recently from a8a2aad to 6268bbc Compare December 7, 2023 08:36
@renovate renovate bot force-pushed the renovate/npm branch 5 times, most recently from a72b03e to aa20c8e Compare December 15, 2023 14:52
@renovate renovate bot force-pushed the renovate/npm branch 2 times, most recently from 640dce7 to af80519 Compare December 20, 2023 02:38
@renovate renovate bot force-pushed the renovate/npm branch 4 times, most recently from 60285bb to c7b9d73 Compare January 2, 2024 05:04
@renovate renovate bot force-pushed the renovate/npm branch 3 times, most recently from 4c83219 to a09ab14 Compare January 10, 2024 05:42
@renovate renovate bot force-pushed the renovate/npm branch 5 times, most recently from a3ce9f2 to ed0554d Compare January 20, 2024 02:36
@coderabbitai
Copy link

coderabbitai bot commented Oct 23, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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? Join our Discord community 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 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.

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.

0 participants