v7.22.5

Compare Source

v7.22.5 (2023-06-08)

🐛 Bug Fix

• babel-preset-env, babel-standalone
  • #​15675 Fix using syntax-unicode-sets-regex in standalone (@​nicolo-ribaudo)

💅 Polish

• babel-core
  • #​15683 Suggest -transform- when resolving missing plugins (@​nicolo-ribaudo)

Committers: 4

• Avery (@​nullableVoidPtr)
• Babel Bot (@​babel-bot)
• Nicolò Ribaudo (@​nicolo-ribaudo)
• @​liuxingbaoyu

v7.22.5

Compare Source

🐛 Bug Fix

• babel-preset-env, babel-standalone
  • #​15675 Fix using syntax-unicode-sets-regex in standalone (@​nicolo-ribaudo)

💅 Polish

• babel-core
  • #​15683 Suggest -transform- when resolving missing plugins (@​nicolo-ribaudo)

v0.53.1

Compare Source

   🚀 Features

• Add vscode delimiters  -  by @​serkodev in https://github.com/unocss/unocss/issues/2728 (3c83e)

   🐞 Bug Fixes

• preset-mini: focus-visible: match, close #​2733  -  by @​antfu in https://github.com/unocss/unocss/issues/2733 (04ae0)
• preset-web-fonts: Fix wrong weight sort  -  by @​zyyv in https://github.com/unocss/unocss/issues/2729 (10724)
• preset-wind: Wrong output for animate-iteration-count  -  by @​enpitsuLin in https://github.com/unocss/unocss/issues/2721 (d45bc)

    View changes on GitHub

v9.1.1

Compare Source

No significant changes

    View changes on GitHub

v8.6.2

Compare Source

Patch Changes

• Change lockfile version back to 6.0 as previous versions of pnpm fail to parse the version correctly #​6648
• When patching a dependency, only consider files specified in the 'files' field of its package.json. Ignore all others #​6565
• Should always treat local file dependency as new dependency #​5381
• Output a warning message when "pnpm" or "resolutions" are configured in a non-root workspace project #​6636

Our Gold Sponsors

Our Silver Sponsors

v8.6.1

Compare Source

Patch Changes

• When dedupe-peer-dependents is enabled (default), use the path (not id) to determine compatibility.

  When multiple dependency groups can be deduplicated, the latter ones are sorted according to number of peers to allow them to benefit from deduplication.

  Resolves: #​6605

• Some minor performance improvements by removing await from loops #​6617.

Our Gold Sponsors

Our Silver Sponsors

v0.25.1

Compare Source

   🐞 Bug Fixes

• Extends types to vue instead of @vue/runtime-core  -  by @​wenfangdu in https://github.com/antfu/unplugin-vue-components/issues/638 (efe0a)

    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

• Support ssr optimizer  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3490 (89842)
• Image type add apng  -  by @​btea in https://github.com/vitest-dev/vitest/issues/3498 (a53c2)
• expect: Support expect.soft  -  by @​Dunqing in https://github.com/vitest-dev/vitest/issues/3507 (7c687)
• runner: Support using function/class as describe/test name  -  by @​fenghan34 in https://github.com/vitest-dev/vitest/issues/3497 (15253)

   🐞 Bug Fixes

• The cli option is passed to coverage.exclude  -  by @​btea in https://github.com/vitest-dev/vitest/issues/3506 (c37cd)
• optimizer: Always respect optimizeDeps even if include/exclude is overridden  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3488 (eb285)
• runner: Ensure Vitest is deduped  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3489 (2deb7)
• ui: Don't cache coverage assets  -  by @​userquin in https://github.com/vitest-dev/vitest/issues/3508 (952b5)
• vite-node: Circular import stuck  -  by @​Dunqing in https://github.com/vitest-dev/vitest/issues/3480 (50f07)
• watch: Junit reporter fails to re-generate report  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3496 (5b73c)

    View changes on GitHub