Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update npm dependencies #28

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: update npm dependencies #28

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 4, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@vitest/coverage-c8 (source) ^0.28.5 -> ^0.33.0 age adoption passing confidence devDependencies minor
eslint (source) ^8.22.0 -> ^9.13.0 age adoption passing confidence devDependencies major
eslint-config-reearth ^0.2.1 -> ^0.3.6 age adoption passing confidence devDependencies minor
node (source) >=12 -> >=20.18.0 age adoption passing confidence engines major
prettier (source) ^2.7.1 -> ^3.3.3 age adoption passing confidence devDependencies major
quickjs-emscripten ^0.21.0 -> ^0.31.0 age adoption passing confidence devDependencies minor
typescript (source) ^4.8.2 -> ^5.6.3 age adoption passing confidence devDependencies major
vite (source) ^4.1.2 -> ^5.4.10 age adoption passing confidence devDependencies major
vite-plugin-dts ^2.0.0-beta.1 -> ^4.3.0 age adoption passing confidence devDependencies major
vitest (source) ^0.28.5 -> ^2.1.3 age adoption passing 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 https://github.com/vitest-dev/vitest/issues/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 https://github.com/vitest-dev/vitest/issues/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 https://github.com/vitest-dev/vitest/issues/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 https://github.com/vitest-dev/vitest/issues/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 https://github.com/vitest-dev/vitest/issues/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

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 d73e3c3 to c45e8d0 Compare October 19, 2024 09:01
@renovate renovate bot force-pushed the renovate/npm branch 2 times, most recently from c074ea1 to a754058 Compare October 23, 2024 23:38
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.


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
🪧 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.

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. (Beta)
  • @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.

@renovate renovate bot force-pushed the renovate/npm branch 3 times, most recently from 85afa4b to 5a168c4 Compare November 2, 2024 08:13
@renovate renovate bot force-pushed the renovate/npm branch 3 times, most recently from c6df7eb to fb2cbd8 Compare November 16, 2024 02:53
@renovate renovate bot force-pushed the renovate/npm branch 3 times, most recently from b9e7a76 to 9e5f2fa Compare November 27, 2024 05:59
@renovate renovate bot force-pushed the renovate/npm branch 3 times, most recently from 5ea0a97 to 248dc8c Compare December 6, 2024 23:44
@renovate renovate bot force-pushed the renovate/npm branch 2 times, most recently from 336a584 to d58848e Compare December 26, 2024 17:57
@renovate renovate bot force-pushed the renovate/npm branch 2 times, most recently from 39f5b4d to 5cfaa90 Compare January 6, 2025 05:36
@renovate renovate bot force-pushed the renovate/npm branch 3 times, most recently from 82ac831 to 897d8fd Compare January 17, 2025 03:22
@renovate renovate bot force-pushed the renovate/npm branch 2 times, most recently from 1e1279f to 74be6a1 Compare January 24, 2025 03:31
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