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 devDependencies #26

Merged
merged 1 commit into from Jun 14, 2023
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 9, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-react-refresh ^0.3.4 -> ^0.4.0 age adoption passing confidence
vitest ^0.30.1 -> ^0.32.0 age adoption passing confidence

Release Notes

ArnaudBarre/eslint-plugin-react-refresh

v0.4.1

Compare Source

  • Ignore export type * (fixes #​12)
  • Support for all-uppercase function wrapped in forwardRef/memo (#​11)

v0.4.0

Compare Source

Add allowConstantExport option (fixes #​8)

This option allow to don't warn when a constant (string, number, boolean, templateLiteral) is exported aside one or more components.

This should be enabled if the fast refresh implementation correctly handles this case (HMR when the constant doesn't change, propagate update to importers when the constant changes). Vite supports it, PR welcome if you notice other integrations works well.

Allow all-uppercase function exports (fixes #​11)

This only works when using direct export. So this pattern doesn't warn anymore:

export const CMS = () => <></>;

But this one will still warn:

const CMS = () => <></>;
export default CMS;
vitest-dev/vitest

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

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies label May 9, 2023
@github-actions
Copy link

github-actions bot commented May 9, 2023

Visit the preview URL for this PR (updated for commit 7ddebcf):

https://brio-so--pr26-renovate-devdependen-pef8t5d5.web.app

(expires Wed, 21 Jun 2023 23:14:36 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 68d280ae20095e94c48ba55225f0362e8bc3ac9d

@renovate renovate bot force-pushed the renovate/devdependencies branch 2 times, most recently from 3dd7880 to d2a3124 Compare May 14, 2023 19:32
@renovate renovate bot force-pushed the renovate/devdependencies branch 2 times, most recently from 627267f to d647643 Compare June 3, 2023 10:15
@renovate renovate bot force-pushed the renovate/devdependencies branch 5 times, most recently from e3a5447 to 3ddb680 Compare June 14, 2023 21:32
@renovate renovate bot force-pushed the renovate/devdependencies branch from 3ddb680 to 7ddebcf Compare June 14, 2023 23:09
@webbertakken webbertakken merged commit 718501e into main Jun 14, 2023
1 check passed
@webbertakken webbertakken deleted the renovate/devdependencies branch June 14, 2023 23:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant