typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
### [`v6.2.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#621-2023-07-31)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.2.0...v6.2.1)
##### Bug Fixes
- **eslint-plugin:** \[no-inferrable-types] apply also for parameter properties ([#7288](https://togithub.com/typescript-eslint/typescript-eslint/issues/7288)) ([67f93b1](https://togithub.com/typescript-eslint/typescript-eslint/commit/67f93b19f2e481a4e441635d72e81de9d5d7ad44))
- **scope-manager:** correct decorators(.length) check in ClassVisitor for methods ([#7334](https://togithub.com/typescript-eslint/typescript-eslint/issues/7334)) ([abbb6c2](https://togithub.com/typescript-eslint/typescript-eslint/commit/abbb6c2c6d2bc1f8d4defd2060dbc473735b2cc7))
You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v6.2.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#621-2023-07-31)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.2.0...v6.2.1)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
evanw/esbuild (esbuild)
### [`v0.18.19`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01819)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.18...v0.18.19)
- Implement `composes` from CSS modules ([#20](https://togithub.com/evanw/esbuild/issues/20))
This release implements the `composes` annotation from the [CSS modules specification](https://togithub.com/css-modules/css-modules#composition). It provides a way for class selectors to reference other class selectors (assuming you are using the `local-css` loader). And with the `from` syntax, this can even work with local names across CSS files. For example:
```js
// app.js
import { submit } from './style.css'
const div = document.createElement('div')
div.className = submit
document.body.appendChild(div)
```
```css
/* style.css */
.button {
composes: pulse from "anim.css";
display: inline-block;
}
.submit {
composes: button;
font-weight: bold;
}
```
```css
/* anim.css */
@keyframes pulse {
from, to { opacity: 1 }
50% { opacity: 0.5 }
}
.pulse {
animation: 2s ease-in-out infinite pulse;
}
```
Bundling this with esbuild using `--bundle --outdir=dist --loader:.css=local-css` now gives the following:
```js
(() => {
// style.css
var submit = "anim_pulse style_button style_submit";
// app.js
var div = document.createElement("div");
div.className = submit;
document.body.appendChild(div);
})();
```
```css
/* anim.css */
@keyframes anim_pulse {
from, to {
opacity: 1;
}
50% {
opacity: 0.5;
}
}
.anim_pulse {
animation: 2s ease-in-out infinite anim_pulse;
}
/* style.css */
.style_button {
display: inline-block;
}
.style_submit {
font-weight: bold;
}
```
Import paths in the `composes: ... from` syntax are resolved using the new `composes-from` import kind, which can be intercepted by plugins during import path resolution when bundling is enabled.
Note that the order in which composed CSS classes from separate files appear in the bundled output file is deliberately ***undefined*** by design (see [the specification](https://togithub.com/css-modules/css-modules#composing-from-other-files) for details). You are not supposed to declare the same CSS property in two separate class selectors and then compose them together. You are only supposed to compose CSS class selectors that declare non-overlapping CSS properties.
Issue [#20](https://togithub.com/evanw/esbuild/issues/20) (the issue tracking CSS modules) is esbuild's most-upvoted issue! With this change, I now consider esbuild's implementation of CSS modules to be complete. There are still improvements to make and there may also be bugs with the current implementation, but these can be tracked in separate issues.
- Fix non-determinism with `tsconfig.json` and symlinks ([#3284](https://togithub.com/evanw/esbuild/issues/3284))
This release fixes an issue that could cause esbuild to sometimes emit incorrect build output in cases where a file under the effect of `tsconfig.json` is inconsistently referenced through a symlink. It can happen when using `npm link` to create a symlink within `node_modules` to an unpublished package. The build result was non-deterministic because esbuild runs module resolution in parallel and the result of the `tsconfig.json` lookup depended on whether the import through the symlink or not through the symlink was resolved first. This problem was fixed by moving the `realpath` operation before the `tsconfig.json` lookup.
- Add a `hash` property to output files ([#3084](https://togithub.com/evanw/esbuild/issues/3084), [#3293](https://togithub.com/evanw/esbuild/issues/3293))
As a convenience, every output file in esbuild's API now includes a `hash` property that is a hash of the `contents` field. This is the hash that's used internally by esbuild to detect changes between builds for esbuild's live-reload feature. You may also use it to detect changes between your own builds if its properties are sufficient for your use case.
This feature has been added directly to output file objects since it's just a hash of the `contents` field, so it makes conceptual sense to store it in the same location. Another benefit of putting it there instead of including it as a part of the watch mode API is that it can be used without watch mode enabled. You can use it to compare the output of two independent builds that were done at different times.
The hash algorithm (currently [XXH64](https://xxhash.com/)) is implementation-dependent and may be changed at any time in between esbuild versions. If you don't like esbuild's choice of hash algorithm then you are welcome to hash the contents yourself instead. As with any hash algorithm, note that while two different hashes mean that the contents are different, two equal hashes do not necessarily mean that the contents are equal. You may still want to compare the contents in addition to the hashes to detect with certainty when output files have been changed.
- Avoid generating duplicate prefixed declarations in CSS ([#3292](https://togithub.com/evanw/esbuild/issues/3292))
There was a request for esbuild's CSS prefixer to avoid generating a prefixed declaration if a declaration by that name is already present in the same rule block. So with this release, esbuild will now avoid doing this:
```css
/* Original code */
body {
backdrop-filter: blur(30px);
-webkit-backdrop-filter: blur(45px);
}
/* Old output (with --target=safari12) */
body {
-webkit-backdrop-filter: blur(30px);
backdrop-filter: blur(30px);
-webkit-backdrop-filter: blur(45px);
}
/* New output (with --target=safari12) */
body {
backdrop-filter: blur(30px);
-webkit-backdrop-filter: blur(45px);
}
```
This can result in a visual difference in certain cases (for example if the browser understands `blur(30px)` but not `blur(45px)`, it will be able to fall back to `blur(30px)`). But this change means esbuild now matches the behavior of [Autoprefixer](https://autoprefixer.github.io/) which is probably a good representation of how people expect this feature to work.
### [`v0.18.18`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01818)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.17...v0.18.18)
- Fix asset references with the `--line-limit` flag ([#3286](https://togithub.com/evanw/esbuild/issues/3286))
The recently-released `--line-limit` flag tells esbuild to terminate long lines after they pass this length limit. This includes automatically wrapping long strings across multiple lines using escaped newline syntax. However, using this could cause esbuild to generate incorrect code for references from generated output files to assets in the bundle (i.e. files loaded with the `file` or `copy` loaders). This is because esbuild implements asset references internally using find-and-replace with a randomly-generated string, but the find operation fails if the string is split by an escaped newline due to line wrapping. This release fixes the problem by not wrapping these strings. This issue affected asset references in both JS and CSS files.
- Support local names in CSS for `@keyframe`, `@counter-style`, and `@container` ([#20](https://togithub.com/evanw/esbuild/issues/20))
This release extends support for local names in CSS files loaded with the `local-css` loader to cover the `@keyframe`, `@counter-style`, and `@container` rules (and also `animation`, `list-style`, and `container` declarations). Here's an example:
```css
@keyframes pulse {
from, to { opacity: 1 }
50% { opacity: 0.5 }
}
@counter-style moon {
system: cyclic;
symbols: 🌕 🌖 🌗 🌘 🌑 🌒 🌓 🌔;
}
@container squish {
li { float: left }
}
ul {
animation: 2s ease-in-out infinite pulse;
list-style: inside moon;
container: squish / size;
}
```
With the `local-css` loader enabled, that CSS will be turned into something like this (with the local name mapping exposed to JS):
```css
@keyframes stdin_pulse {
from, to {
opacity: 1;
}
50% {
opacity: 0.5;
}
}
@counter-style stdin_moon {
system: cyclic;
symbols: 🌕 🌖 🌗 🌘 🌑 🌒 🌓 🌔;
}
@container stdin_squish {
li {
float: left;
}
}
ul {
animation: 2s ease-in-out infinite stdin_pulse;
list-style: inside stdin_moon;
container: stdin_squish / size;
}
```
If you want to use a global name within a file loaded with the `local-css` loader, you can use a `:global` selector to do that:
```css
div {
/* All symbols are global inside this scope (i.e.
* "pulse", "moon", and "squish" are global below) */
:global {
animation: 2s ease-in-out infinite pulse;
list-style: inside moon;
container: squish / size;
}
}
```
If you want to use `@keyframes`, `@counter-style`, or `@container` with a global name, make sure it's in a file that uses the `css` or `global-css` loader instead of the `local-css` loader. For example, you can configure `--loader:.module.css=local-css` so that the `local-css` loader only applies to `*.module.css` files.
- Support strings as keyframe animation names in CSS ([#2555](https://togithub.com/evanw/esbuild/issues/2555))
With this release, esbuild will now parse animation names that are specified as strings and will convert them to identifiers. The CSS specification allows animation names to be specified using either identifiers or strings but Chrome only understands identifiers, so esbuild will now always convert string names to identifier names for Chrome compatibility:
```css
/* Original code */
@keyframes "hide menu" {
from { opacity: 1 }
to { opacity: 0 }
}
menu.hide {
animation: 0.5s ease-in-out "hide menu";
}
/* Old output */
@keyframes "hide menu" { from { opacity: 1 } to { opacity: 0 } }
menu.hide {
animation: 0.5s ease-in-out "hide menu";
}
/* New output */
@keyframes hide\ menu {
from {
opacity: 1;
}
to {
opacity: 0;
}
}
menu.hide {
animation: 0.5s ease-in-out hide\ menu;
}
```
prettier/prettier (prettier)
### [`v3.0.1`](https://togithub.com/prettier/prettier/blob/HEAD/CHANGELOG.md#301)
[Compare Source](https://togithub.com/prettier/prettier/compare/3.0.0...3.0.1)
[diff](https://togithub.com/prettier/prettier/compare/3.0.0...3.0.1)
##### Fix cursor positioning for a special case ([#14812](https://togithub.com/prettier/prettier/pull/14812) by [@fisker](https://togithub.com/fisker))
```js
// <|> is the cursor position
/* Input */
// All messages are represented in JSON.
// So, the prettier.py controls a subprocess which spawns "node {this_file}".
import {<|> } from "fs"
/* Prettier 3.0.0 */
// All messages are represented in JSON.
// So, the prettier.py <|>controls a subprocess which spawns "node {this_file}".
import {} from "fs"
/* Prettier 3.0.1 */
// All messages are represented in JSON.
// So, the prettier.py controls a subprocess which spawns "node {this_file}".
import {<|>} from "fs"
```
##### Fix plugins/estree.d.ts to make it a module ([#15018](https://togithub.com/prettier/prettier/pull/15018) by [@kingyue737](https://togithub.com/kingyue737))
Add `export {}` in `plugins/estree.d.ts` to fix the "File is not a module" error
##### Add parenthesis around leading multiline comment in return statement ([#15037](https://togithub.com/prettier/prettier/pull/15037) by [@auvred](https://togithub.com/auvred))
```jsx
// Input
function fn() {
return (
/**
* @type {...}
*/ expresssion
)
}
// Prettier 3.0.0
function fn() {
return /**
* @type {...}
*/ expresssion;
}
// Prettier 3.0.1
function fn() {
return (
/**
* @type {...}
*/ expresssion
);
}
```
##### Add support for Vue "Generic Components" ([#15066](https://togithub.com/prettier/prettier/pull/15066) by [@auvred](https://togithub.com/auvred))
https://blog.vuejs.org/posts/vue-3-3#generic-components
```vue
```
##### Fix comments print in `IfStatement` ([#15076](https://togithub.com/prettier/prettier/pull/15076) by [@fisker](https://togithub.com/fisker))
```js
function a(b) {
if (b) return 1; // comment
else return 2;
}
/* Prettier 3.0.0 */
Error: Comment "comment" was not printed. Please report this error!
/* Prettier 3.0.1 */
function a(b) {
if (b) return 1; // comment
else return 2;
}
```
##### Add missing type definition for `printer.preprocess` ([#15123](https://togithub.com/prettier/prettier/pull/15123) by [@so1ve](https://togithub.com/so1ve))
```diff
export interface Printer {
// ...
+ preprocess?:
+ | ((ast: T, options: ParserOptions) => T | Promise)
+ | undefined;
}
```
##### Add missing `getVisitorKeys` method type definition for `Printer` ([#15125](https://togithub.com/prettier/prettier/pull/15125) by [@auvred](https://togithub.com/auvred))
```tsx
const printer: Printer = {
print: () => [],
getVisitorKeys(node, nonTraversableKeys) {
return ["body"];
},
};
```
##### Add typing to support `readonly` array properties of AST Node ([#15127](https://togithub.com/prettier/prettier/pull/15127) by [@auvred](https://togithub.com/auvred))
```tsx
// Input
interface TestNode {
readonlyArray: readonly string[];
}
declare const path: AstPath;
path.map(() => "", "readonlyArray");
// Prettier 3.0.0
interface TestNode {
readonlyArray: readonly string[];
}
declare const path: AstPath;
path.map(() => "", "readonlyArray");
// ^ Argument of type '"readonlyArray"' is not assignable to parameter of type '"regularArray"'. ts(2345)
// Prettier 3.0.1
interface TestNode {
readonlyArray: readonly string[];
}
declare const path: AstPath;
path.map(() => "", "readonlyArray");
```
##### Add space before unary minus followed by a function call ([#15129](https://togithub.com/prettier/prettier/pull/15129) by [@pamelalozano](https://togithub.com/pamelalozano))
```less
// Input
div {
margin: - func();
}
// Prettier 3.0.0
div {
margin: -func();
}
// Prettier 3.0.1
div {
margin: - func();
}
```
egoist/tsup (tsup)
### [`v7.2.0`](https://togithub.com/egoist/tsup/releases/tag/v7.2.0)
[Compare Source](https://togithub.com/egoist/tsup/compare/v7.1.0...v7.2.0)
##### Bug Fixes
- allow to kill onSuccess process using SIGKILL signal, closes [#936](https://togithub.com/egoist/tsup/issues/936) ([612cabf](https://togithub.com/egoist/tsup/commit/612cabf1c1b99709d5d16c6e861ec12dae3db455))
##### Features
- add option for interop default in cjs ([#947](https://togithub.com/egoist/tsup/issues/947)) ([d870f4e](https://togithub.com/egoist/tsup/commit/d870f4e76cf0ff89a83e90bdc4931aa30bddb536))
vitest-dev/vitest (vitest)
### [`v0.34.1`](https://togithub.com/vitest-dev/vitest/releases/tag/v0.34.1)
[Compare Source](https://togithub.com/vitest-dev/vitest/compare/v0.34.0...v0.34.1)
##### 🐞 Bug Fixes
- Pass `--experimental-vm-worker-memory-limit` to `tinypool` - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3856](https://togithub.com/vitest-dev/vitest/issues/3856) [(3c67a)](https://togithub.com/vitest-dev/vitest/commit/3c67a4cb)
##### [View changes on GitHub](https://togithub.com/vitest-dev/vitest/compare/v0.34.0...v0.34.1)
### [`v0.34.0`](https://togithub.com/vitest-dev/vitest/releases/tag/v0.34.0)
[Compare Source](https://togithub.com/vitest-dev/vitest/compare/v0.33.0...v0.34.0)
##### 🚨 Breaking Changes
- Transform mode affects only test files, not regular files - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3491](https://togithub.com/vitest-dev/vitest/issues/3491) [(9608b)](https://togithub.com/vitest-dev/vitest/commit/9608bf72)
- `transformMode` is now moved to `server.transformMode`. This option is highly discouraged to use. If you need to change the transform mode, use the new option `testTransformMode` instead to control the mode based on the running test, not the current file path. By default, tests with `jsdom` or `happy-dom` use `web` transform mode, and tests using `node` or `edge` environment use `ssr` mode. If you have a custom environment, it should provide `transformMode` property.
- Disable `coverage.reportOnFailure` by default - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3615](https://togithub.com/vitest-dev/vitest/issues/3615) [(0c6f6)](https://togithub.com/vitest-dev/vitest/commit/0c6f624f)
- Remove `@vitest/coverage-c8` package - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3614](https://togithub.com/vitest-dev/vitest/issues/3614) [(a90d6)](https://togithub.com/vitest-dev/vitest/commit/a90d64fe)
- `@vitest/coverage-c8` is no longer supported. Please, use `@vitest/coverage-v8` instead.
- Support running tests using VM context - by [@sheremet-va](https://togithub.com/sheremet-va) and [@dammy001](https://togithub.com/dammy001) in [https://github.com/vitest-dev/vitest/issues/3203](https://togithub.com/vitest-dev/vitest/issues/3203) [(b0929)](https://togithub.com/vitest-dev/vitest/commit/b0929852)
- To address speed issues in some applications, Vitest now provides `experimentalVmThreads` pool to run your tests using VM Sandboxes environment. Make sure you understand [all pitfalls](https://vitest.dev/config/#experimentalvmthreads) of this pool before opening an issue.
- Introduce `server` option - by [@fenghan34](https://togithub.com/fenghan34) and [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3725](https://togithub.com/vitest-dev/vitest/issues/3725) [(dc4fa)](https://togithub.com/vitest-dev/vitest/commit/dc4faf64)
- Most of `deps.` options are now moved to `server.deps` with a deprecation warning. Please, consider using `deps.optimizer` instead of `deps.inline`/`deps.external`. Ideally, we would like to move away from using `server.deps.inline` altogether.
- **vite-node**: Make CLI arguments parsing behavior consistent with node/tsx/ts-node - by [@rxliuli](https://togithub.com/rxliuli) in [https://github.com/vitest-dev/vitest/issues/3574](https://togithub.com/vitest-dev/vitest/issues/3574) [(1cd4e)](https://togithub.com/vitest-dev/vitest/commit/1cd4eb0f)
- You now have to provide CLI arguments before the entry point. For example, instead of `vite-node index.ts --watch`, you now have to do `vite-node --watch index.ts`.
- Add preact example, remove optimizer experimental status, enable by default - by [@sheremet-va](https://togithub.com/sheremet-va) and [@eryue0220](https://togithub.com/eryue0220) in [https://github.com/vitest-dev/vitest/issues/3854](https://togithub.com/vitest-dev/vitest/issues/3854) [(4b946)](https://togithub.com/vitest-dev/vitest/commit/4b946ca9)
- `deps.optimizer` is now enabled by default. This means that Vitest will bundle specified dependencies before running your tests. This field inherits options from `optimizeDeps` and `ssr.optimizeDeps` which are populated by other plugins (like, Svelte).
##### 🚀 Features
- Support `describe.sequential` - by [@fenghan34](https://togithub.com/fenghan34) and [@dammy001](https://togithub.com/dammy001) in [https://github.com/vitest-dev/vitest/issues/3771](https://togithub.com/vitest-dev/vitest/issues/3771) [(86934)](https://togithub.com/vitest-dev/vitest/commit/8693449b)
- Support config junit reporter className with env - by [@InfiniteXyy](https://togithub.com/InfiniteXyy) in [https://github.com/vitest-dev/vitest/issues/3808](https://togithub.com/vitest-dev/vitest/issues/3808) [(e8bc4)](https://togithub.com/vitest-dev/vitest/commit/e8bc46b6)
- Running vitest with `--related --watch` reruns non-affected tests if they were changed during a run - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3844](https://togithub.com/vitest-dev/vitest/issues/3844) [(c9aea)](https://togithub.com/vitest-dev/vitest/commit/c9aeac4c)
##### 🐞 Bug Fixes
- Isolate workers between envs and workspaces - by [@AriPerkkio](https://togithub.com/AriPerkkio) [(ed4e0)](https://togithub.com/vitest-dev/vitest/commit/ed4e0424)
- Modify condition - by [@btea](https://togithub.com/btea) [(a78e6)](https://togithub.com/vitest-dev/vitest/commit/a78e6bd0)
- Module Graph view is blocking the Console view - by [@g4rry420](https://togithub.com/g4rry420) [(3b5f9)](https://togithub.com/vitest-dev/vitest/commit/3b5f96bc)
- Port the latest `defineConfig` type from vite - by [@sodatea](https://togithub.com/sodatea) in [https://github.com/vitest-dev/vitest/issues/3804](https://togithub.com/vitest-dev/vitest/issues/3804) [(9c8e3)](https://togithub.com/vitest-dev/vitest/commit/9c8e3083)
- Don't overwrite Node.js URL global - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3828](https://togithub.com/vitest-dev/vitest/issues/3828) [(cdab4)](https://togithub.com/vitest-dev/vitest/commit/cdab4651)
- ForceRerunTriggers correctly triggers a rerun - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3829](https://togithub.com/vitest-dev/vitest/issues/3829) [(17988)](https://togithub.com/vitest-dev/vitest/commit/17988e51)
- **browser**:
- Don't inline magic-string and estree-walker - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3726](https://togithub.com/vitest-dev/vitest/issues/3726) [(ee937)](https://togithub.com/vitest-dev/vitest/commit/ee93762a)
- Multi-suite coverage - by [@elby22](https://togithub.com/elby22) in [https://github.com/vitest-dev/vitest/issues/3806](https://togithub.com/vitest-dev/vitest/issues/3806) [(5de9a)](https://togithub.com/vitest-dev/vitest/commit/5de9af26)
- **core**:
- DataView comparison does not work in `toStrictEqual` - by [@Dunqing](https://togithub.com/Dunqing) [(52aef)](https://togithub.com/vitest-dev/vitest/commit/52aef92e)
- **coverage**:
- V8 provider to pick source maps without url query params - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3784](https://togithub.com/vitest-dev/vitest/issues/3784) [(280e6)](https://togithub.com/vitest-dev/vitest/commit/280e6745)
- Update `istanbul-lib-instrument` to v6 to fix vulnerable dependency - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3814](https://togithub.com/vitest-dev/vitest/issues/3814) [(f3bd9)](https://togithub.com/vitest-dev/vitest/commit/f3bd9102)
- Exclude vite virtual modules by default - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3794](https://togithub.com/vitest-dev/vitest/issues/3794) [(3c851)](https://togithub.com/vitest-dev/vitest/commit/3c851872)
- **node**:
- Guard error info - by [@btea](https://togithub.com/btea) [(88b39)](https://togithub.com/vitest-dev/vitest/commit/88b39758)
- **vite-node**:
- Always treat node_modules as modulesDirectory - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3830](https://togithub.com/vitest-dev/vitest/issues/3830) [(51ab8)](https://togithub.com/vitest-dev/vitest/commit/51ab8d6c)
- Normalize drive letter to keep the same reference to a module - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3836](https://togithub.com/vitest-dev/vitest/issues/3836) [(45521)](https://togithub.com/vitest-dev/vitest/commit/45521859)
- Correctly resolve hmr filepath - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3834](https://togithub.com/vitest-dev/vitest/issues/3834) [(711a6)](https://togithub.com/vitest-dev/vitest/commit/711a6249)
- **watch**:
- Clear screen on all terminals - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3661](https://togithub.com/vitest-dev/vitest/issues/3661) [(8bd26)](https://togithub.com/vitest-dev/vitest/commit/8bd26b01)
##### 🏎 Performance
- Deprecate deps.registerNodeLoader - by [@sheremet-va](https://togithub.com/sheremet-va) [(7f45b)](https://togithub.com/vitest-dev/vitest/commit/7f45bf2d)
- This option was introduced to support aliasing inside external packages. Please, use `deps.optimizer.web` instead. If you test Node.js applications, consider adding external packages to `server.deps.inline`.
##### [View changes on GitHub](https://togithub.com/vitest-dev/vitest/compare/v0.33.0...v0.34.0)
Configuration
📅 Schedule: Branch creation - "before 12pm on Sunday" (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 has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
^18.17.1->^18.17.3^6.2.0->^6.2.1^6.2.0->^6.2.1^0.18.17->^0.18.19^3.0.0->^3.0.1^7.1.0->^7.2.0^0.33.0->^0.34.1Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
### [`v6.2.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#621-2023-07-31) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.2.0...v6.2.1) ##### Bug Fixes - **eslint-plugin:** \[no-inferrable-types] apply also for parameter properties ([#7288](https://togithub.com/typescript-eslint/typescript-eslint/issues/7288)) ([67f93b1](https://togithub.com/typescript-eslint/typescript-eslint/commit/67f93b19f2e481a4e441635d72e81de9d5d7ad44)) - **scope-manager:** correct decorators(.length) check in ClassVisitor for methods ([#7334](https://togithub.com/typescript-eslint/typescript-eslint/issues/7334)) ([abbb6c2](https://togithub.com/typescript-eslint/typescript-eslint/commit/abbb6c2c6d2bc1f8d4defd2060dbc473735b2cc7)) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v6.2.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#621-2023-07-31) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.2.0...v6.2.1) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.evanw/esbuild (esbuild)
### [`v0.18.19`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01819) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.18...v0.18.19) - Implement `composes` from CSS modules ([#20](https://togithub.com/evanw/esbuild/issues/20)) This release implements the `composes` annotation from the [CSS modules specification](https://togithub.com/css-modules/css-modules#composition). It provides a way for class selectors to reference other class selectors (assuming you are using the `local-css` loader). And with the `from` syntax, this can even work with local names across CSS files. For example: ```js // app.js import { submit } from './style.css' const div = document.createElement('div') div.className = submit document.body.appendChild(div) ``` ```css /* style.css */ .button { composes: pulse from "anim.css"; display: inline-block; } .submit { composes: button; font-weight: bold; } ``` ```css /* anim.css */ @keyframes pulse { from, to { opacity: 1 } 50% { opacity: 0.5 } } .pulse { animation: 2s ease-in-out infinite pulse; } ``` Bundling this with esbuild using `--bundle --outdir=dist --loader:.css=local-css` now gives the following: ```js (() => { // style.css var submit = "anim_pulse style_button style_submit"; // app.js var div = document.createElement("div"); div.className = submit; document.body.appendChild(div); })(); ``` ```css /* anim.css */ @keyframes anim_pulse { from, to { opacity: 1; } 50% { opacity: 0.5; } } .anim_pulse { animation: 2s ease-in-out infinite anim_pulse; } /* style.css */ .style_button { display: inline-block; } .style_submit { font-weight: bold; } ``` Import paths in the `composes: ... from` syntax are resolved using the new `composes-from` import kind, which can be intercepted by plugins during import path resolution when bundling is enabled. Note that the order in which composed CSS classes from separate files appear in the bundled output file is deliberately ***undefined*** by design (see [the specification](https://togithub.com/css-modules/css-modules#composing-from-other-files) for details). You are not supposed to declare the same CSS property in two separate class selectors and then compose them together. You are only supposed to compose CSS class selectors that declare non-overlapping CSS properties. Issue [#20](https://togithub.com/evanw/esbuild/issues/20) (the issue tracking CSS modules) is esbuild's most-upvoted issue! With this change, I now consider esbuild's implementation of CSS modules to be complete. There are still improvements to make and there may also be bugs with the current implementation, but these can be tracked in separate issues. - Fix non-determinism with `tsconfig.json` and symlinks ([#3284](https://togithub.com/evanw/esbuild/issues/3284)) This release fixes an issue that could cause esbuild to sometimes emit incorrect build output in cases where a file under the effect of `tsconfig.json` is inconsistently referenced through a symlink. It can happen when using `npm link` to create a symlink within `node_modules` to an unpublished package. The build result was non-deterministic because esbuild runs module resolution in parallel and the result of the `tsconfig.json` lookup depended on whether the import through the symlink or not through the symlink was resolved first. This problem was fixed by moving the `realpath` operation before the `tsconfig.json` lookup. - Add a `hash` property to output files ([#3084](https://togithub.com/evanw/esbuild/issues/3084), [#3293](https://togithub.com/evanw/esbuild/issues/3293)) As a convenience, every output file in esbuild's API now includes a `hash` property that is a hash of the `contents` field. This is the hash that's used internally by esbuild to detect changes between builds for esbuild's live-reload feature. You may also use it to detect changes between your own builds if its properties are sufficient for your use case. This feature has been added directly to output file objects since it's just a hash of the `contents` field, so it makes conceptual sense to store it in the same location. Another benefit of putting it there instead of including it as a part of the watch mode API is that it can be used without watch mode enabled. You can use it to compare the output of two independent builds that were done at different times. The hash algorithm (currently [XXH64](https://xxhash.com/)) is implementation-dependent and may be changed at any time in between esbuild versions. If you don't like esbuild's choice of hash algorithm then you are welcome to hash the contents yourself instead. As with any hash algorithm, note that while two different hashes mean that the contents are different, two equal hashes do not necessarily mean that the contents are equal. You may still want to compare the contents in addition to the hashes to detect with certainty when output files have been changed. - Avoid generating duplicate prefixed declarations in CSS ([#3292](https://togithub.com/evanw/esbuild/issues/3292)) There was a request for esbuild's CSS prefixer to avoid generating a prefixed declaration if a declaration by that name is already present in the same rule block. So with this release, esbuild will now avoid doing this: ```css /* Original code */ body { backdrop-filter: blur(30px); -webkit-backdrop-filter: blur(45px); } /* Old output (with --target=safari12) */ body { -webkit-backdrop-filter: blur(30px); backdrop-filter: blur(30px); -webkit-backdrop-filter: blur(45px); } /* New output (with --target=safari12) */ body { backdrop-filter: blur(30px); -webkit-backdrop-filter: blur(45px); } ``` This can result in a visual difference in certain cases (for example if the browser understands `blur(30px)` but not `blur(45px)`, it will be able to fall back to `blur(30px)`). But this change means esbuild now matches the behavior of [Autoprefixer](https://autoprefixer.github.io/) which is probably a good representation of how people expect this feature to work. ### [`v0.18.18`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01818) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.17...v0.18.18) - Fix asset references with the `--line-limit` flag ([#3286](https://togithub.com/evanw/esbuild/issues/3286)) The recently-released `--line-limit` flag tells esbuild to terminate long lines after they pass this length limit. This includes automatically wrapping long strings across multiple lines using escaped newline syntax. However, using this could cause esbuild to generate incorrect code for references from generated output files to assets in the bundle (i.e. files loaded with the `file` or `copy` loaders). This is because esbuild implements asset references internally using find-and-replace with a randomly-generated string, but the find operation fails if the string is split by an escaped newline due to line wrapping. This release fixes the problem by not wrapping these strings. This issue affected asset references in both JS and CSS files. - Support local names in CSS for `@keyframe`, `@counter-style`, and `@container` ([#20](https://togithub.com/evanw/esbuild/issues/20)) This release extends support for local names in CSS files loaded with the `local-css` loader to cover the `@keyframe`, `@counter-style`, and `@container` rules (and also `animation`, `list-style`, and `container` declarations). Here's an example: ```css @keyframes pulse { from, to { opacity: 1 } 50% { opacity: 0.5 } } @counter-style moon { system: cyclic; symbols: 🌕 🌖 🌗 🌘 🌑 🌒 🌓 🌔; } @container squish { li { float: left } } ul { animation: 2s ease-in-out infinite pulse; list-style: inside moon; container: squish / size; } ``` With the `local-css` loader enabled, that CSS will be turned into something like this (with the local name mapping exposed to JS): ```css @keyframes stdin_pulse { from, to { opacity: 1; } 50% { opacity: 0.5; } } @counter-style stdin_moon { system: cyclic; symbols: 🌕 🌖 🌗 🌘 🌑 🌒 🌓 🌔; } @container stdin_squish { li { float: left; } } ul { animation: 2s ease-in-out infinite stdin_pulse; list-style: inside stdin_moon; container: stdin_squish / size; } ``` If you want to use a global name within a file loaded with the `local-css` loader, you can use a `:global` selector to do that: ```css div { /* All symbols are global inside this scope (i.e. * "pulse", "moon", and "squish" are global below) */ :global { animation: 2s ease-in-out infinite pulse; list-style: inside moon; container: squish / size; } } ``` If you want to use `@keyframes`, `@counter-style`, or `@container` with a global name, make sure it's in a file that uses the `css` or `global-css` loader instead of the `local-css` loader. For example, you can configure `--loader:.module.css=local-css` so that the `local-css` loader only applies to `*.module.css` files. - Support strings as keyframe animation names in CSS ([#2555](https://togithub.com/evanw/esbuild/issues/2555)) With this release, esbuild will now parse animation names that are specified as strings and will convert them to identifiers. The CSS specification allows animation names to be specified using either identifiers or strings but Chrome only understands identifiers, so esbuild will now always convert string names to identifier names for Chrome compatibility: ```css /* Original code */ @keyframes "hide menu" { from { opacity: 1 } to { opacity: 0 } } menu.hide { animation: 0.5s ease-in-out "hide menu"; } /* Old output */ @keyframes "hide menu" { from { opacity: 1 } to { opacity: 0 } } menu.hide { animation: 0.5s ease-in-out "hide menu"; } /* New output */ @keyframes hide\ menu { from { opacity: 1; } to { opacity: 0; } } menu.hide { animation: 0.5s ease-in-out hide\ menu; } ```prettier/prettier (prettier)
### [`v3.0.1`](https://togithub.com/prettier/prettier/blob/HEAD/CHANGELOG.md#301) [Compare Source](https://togithub.com/prettier/prettier/compare/3.0.0...3.0.1) [diff](https://togithub.com/prettier/prettier/compare/3.0.0...3.0.1) ##### Fix cursor positioning for a special case ([#14812](https://togithub.com/prettier/prettier/pull/14812) by [@fisker](https://togithub.com/fisker)) ```js // <|> is the cursor position /* Input */ // All messages are represented in JSON. // So, the prettier.py controls a subprocess which spawns "node {this_file}". import {<|> } from "fs" /* Prettier 3.0.0 */ // All messages are represented in JSON. // So, the prettier.py <|>controls a subprocess which spawns "node {this_file}". import {} from "fs" /* Prettier 3.0.1 */ // All messages are represented in JSON. // So, the prettier.py controls a subprocess which spawns "node {this_file}". import {<|>} from "fs" ``` ##### Fix plugins/estree.d.ts to make it a module ([#15018](https://togithub.com/prettier/prettier/pull/15018) by [@kingyue737](https://togithub.com/kingyue737)) Add `export {}` in `plugins/estree.d.ts` to fix the "File is not a module" error ##### Add parenthesis around leading multiline comment in return statement ([#15037](https://togithub.com/prettier/prettier/pull/15037) by [@auvred](https://togithub.com/auvred)) ```jsx // Input function fn() { return ( /** * @type {...} */ expresssion ) } // Prettier 3.0.0 function fn() { return /** * @type {...} */ expresssion; } // Prettier 3.0.1 function fn() { return ( /** * @type {...} */ expresssion ); } ``` ##### Add support for Vue "Generic Components" ([#15066](https://togithub.com/prettier/prettier/pull/15066) by [@auvred](https://togithub.com/auvred)) https://blog.vuejs.org/posts/vue-3-3#generic-components ```vue ``` ##### Fix comments print in `IfStatement` ([#15076](https://togithub.com/prettier/prettier/pull/15076) by [@fisker](https://togithub.com/fisker)) ```js function a(b) { if (b) return 1; // comment else return 2; } /* Prettier 3.0.0 */ Error: Comment "comment" was not printed. Please report this error! /* Prettier 3.0.1 */ function a(b) { if (b) return 1; // comment else return 2; } ``` ##### Add missing type definition for `printer.preprocess` ([#15123](https://togithub.com/prettier/prettier/pull/15123) by [@so1ve](https://togithub.com/so1ve)) ```diff export interface Printeregoist/tsup (tsup)
### [`v7.2.0`](https://togithub.com/egoist/tsup/releases/tag/v7.2.0) [Compare Source](https://togithub.com/egoist/tsup/compare/v7.1.0...v7.2.0) ##### Bug Fixes - allow to kill onSuccess process using SIGKILL signal, closes [#936](https://togithub.com/egoist/tsup/issues/936) ([612cabf](https://togithub.com/egoist/tsup/commit/612cabf1c1b99709d5d16c6e861ec12dae3db455)) ##### Features - add option for interop default in cjs ([#947](https://togithub.com/egoist/tsup/issues/947)) ([d870f4e](https://togithub.com/egoist/tsup/commit/d870f4e76cf0ff89a83e90bdc4931aa30bddb536))vitest-dev/vitest (vitest)
### [`v0.34.1`](https://togithub.com/vitest-dev/vitest/releases/tag/v0.34.1) [Compare Source](https://togithub.com/vitest-dev/vitest/compare/v0.34.0...v0.34.1) ##### 🐞 Bug Fixes - Pass `--experimental-vm-worker-memory-limit` to `tinypool` - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3856](https://togithub.com/vitest-dev/vitest/issues/3856) [(3c67a)](https://togithub.com/vitest-dev/vitest/commit/3c67a4cb) ##### [View changes on GitHub](https://togithub.com/vitest-dev/vitest/compare/v0.34.0...v0.34.1) ### [`v0.34.0`](https://togithub.com/vitest-dev/vitest/releases/tag/v0.34.0) [Compare Source](https://togithub.com/vitest-dev/vitest/compare/v0.33.0...v0.34.0) ##### 🚨 Breaking Changes - Transform mode affects only test files, not regular files - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3491](https://togithub.com/vitest-dev/vitest/issues/3491) [(9608b)](https://togithub.com/vitest-dev/vitest/commit/9608bf72) - `transformMode` is now moved to `server.transformMode`. This option is highly discouraged to use. If you need to change the transform mode, use the new option `testTransformMode` instead to control the mode based on the running test, not the current file path. By default, tests with `jsdom` or `happy-dom` use `web` transform mode, and tests using `node` or `edge` environment use `ssr` mode. If you have a custom environment, it should provide `transformMode` property. - Disable `coverage.reportOnFailure` by default - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3615](https://togithub.com/vitest-dev/vitest/issues/3615) [(0c6f6)](https://togithub.com/vitest-dev/vitest/commit/0c6f624f) - Remove `@vitest/coverage-c8` package - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3614](https://togithub.com/vitest-dev/vitest/issues/3614) [(a90d6)](https://togithub.com/vitest-dev/vitest/commit/a90d64fe) - `@vitest/coverage-c8` is no longer supported. Please, use `@vitest/coverage-v8` instead. - Support running tests using VM context - by [@sheremet-va](https://togithub.com/sheremet-va) and [@dammy001](https://togithub.com/dammy001) in [https://github.com/vitest-dev/vitest/issues/3203](https://togithub.com/vitest-dev/vitest/issues/3203) [(b0929)](https://togithub.com/vitest-dev/vitest/commit/b0929852) - To address speed issues in some applications, Vitest now provides `experimentalVmThreads` pool to run your tests using VM Sandboxes environment. Make sure you understand [all pitfalls](https://vitest.dev/config/#experimentalvmthreads) of this pool before opening an issue. - Introduce `server` option - by [@fenghan34](https://togithub.com/fenghan34) and [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3725](https://togithub.com/vitest-dev/vitest/issues/3725) [(dc4fa)](https://togithub.com/vitest-dev/vitest/commit/dc4faf64) - Most of `deps.` options are now moved to `server.deps` with a deprecation warning. Please, consider using `deps.optimizer` instead of `deps.inline`/`deps.external`. Ideally, we would like to move away from using `server.deps.inline` altogether. - **vite-node**: Make CLI arguments parsing behavior consistent with node/tsx/ts-node - by [@rxliuli](https://togithub.com/rxliuli) in [https://github.com/vitest-dev/vitest/issues/3574](https://togithub.com/vitest-dev/vitest/issues/3574) [(1cd4e)](https://togithub.com/vitest-dev/vitest/commit/1cd4eb0f) - You now have to provide CLI arguments before the entry point. For example, instead of `vite-node index.ts --watch`, you now have to do `vite-node --watch index.ts`. - Add preact example, remove optimizer experimental status, enable by default - by [@sheremet-va](https://togithub.com/sheremet-va) and [@eryue0220](https://togithub.com/eryue0220) in [https://github.com/vitest-dev/vitest/issues/3854](https://togithub.com/vitest-dev/vitest/issues/3854) [(4b946)](https://togithub.com/vitest-dev/vitest/commit/4b946ca9) - `deps.optimizer` is now enabled by default. This means that Vitest will bundle specified dependencies before running your tests. This field inherits options from `optimizeDeps` and `ssr.optimizeDeps` which are populated by other plugins (like, Svelte). ##### 🚀 Features - Support `describe.sequential` - by [@fenghan34](https://togithub.com/fenghan34) and [@dammy001](https://togithub.com/dammy001) in [https://github.com/vitest-dev/vitest/issues/3771](https://togithub.com/vitest-dev/vitest/issues/3771) [(86934)](https://togithub.com/vitest-dev/vitest/commit/8693449b) - Support config junit reporter className with env - by [@InfiniteXyy](https://togithub.com/InfiniteXyy) in [https://github.com/vitest-dev/vitest/issues/3808](https://togithub.com/vitest-dev/vitest/issues/3808) [(e8bc4)](https://togithub.com/vitest-dev/vitest/commit/e8bc46b6) - Running vitest with `--related --watch` reruns non-affected tests if they were changed during a run - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3844](https://togithub.com/vitest-dev/vitest/issues/3844) [(c9aea)](https://togithub.com/vitest-dev/vitest/commit/c9aeac4c) ##### 🐞 Bug Fixes - Isolate workers between envs and workspaces - by [@AriPerkkio](https://togithub.com/AriPerkkio) [(ed4e0)](https://togithub.com/vitest-dev/vitest/commit/ed4e0424) - Modify condition - by [@btea](https://togithub.com/btea) [(a78e6)](https://togithub.com/vitest-dev/vitest/commit/a78e6bd0) - Module Graph view is blocking the Console view - by [@g4rry420](https://togithub.com/g4rry420) [(3b5f9)](https://togithub.com/vitest-dev/vitest/commit/3b5f96bc) - Port the latest `defineConfig` type from vite - by [@sodatea](https://togithub.com/sodatea) in [https://github.com/vitest-dev/vitest/issues/3804](https://togithub.com/vitest-dev/vitest/issues/3804) [(9c8e3)](https://togithub.com/vitest-dev/vitest/commit/9c8e3083) - Don't overwrite Node.js URL global - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3828](https://togithub.com/vitest-dev/vitest/issues/3828) [(cdab4)](https://togithub.com/vitest-dev/vitest/commit/cdab4651) - ForceRerunTriggers correctly triggers a rerun - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3829](https://togithub.com/vitest-dev/vitest/issues/3829) [(17988)](https://togithub.com/vitest-dev/vitest/commit/17988e51) - **browser**: - Don't inline magic-string and estree-walker - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3726](https://togithub.com/vitest-dev/vitest/issues/3726) [(ee937)](https://togithub.com/vitest-dev/vitest/commit/ee93762a) - Multi-suite coverage - by [@elby22](https://togithub.com/elby22) in [https://github.com/vitest-dev/vitest/issues/3806](https://togithub.com/vitest-dev/vitest/issues/3806) [(5de9a)](https://togithub.com/vitest-dev/vitest/commit/5de9af26) - **core**: - DataView comparison does not work in `toStrictEqual` - by [@Dunqing](https://togithub.com/Dunqing) [(52aef)](https://togithub.com/vitest-dev/vitest/commit/52aef92e) - **coverage**: - V8 provider to pick source maps without url query params - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3784](https://togithub.com/vitest-dev/vitest/issues/3784) [(280e6)](https://togithub.com/vitest-dev/vitest/commit/280e6745) - Update `istanbul-lib-instrument` to v6 to fix vulnerable dependency - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3814](https://togithub.com/vitest-dev/vitest/issues/3814) [(f3bd9)](https://togithub.com/vitest-dev/vitest/commit/f3bd9102) - Exclude vite virtual modules by default - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3794](https://togithub.com/vitest-dev/vitest/issues/3794) [(3c851)](https://togithub.com/vitest-dev/vitest/commit/3c851872) - **node**: - Guard error info - by [@btea](https://togithub.com/btea) [(88b39)](https://togithub.com/vitest-dev/vitest/commit/88b39758) - **vite-node**: - Always treat node_modules as modulesDirectory - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3830](https://togithub.com/vitest-dev/vitest/issues/3830) [(51ab8)](https://togithub.com/vitest-dev/vitest/commit/51ab8d6c) - Normalize drive letter to keep the same reference to a module - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3836](https://togithub.com/vitest-dev/vitest/issues/3836) [(45521)](https://togithub.com/vitest-dev/vitest/commit/45521859) - Correctly resolve hmr filepath - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3834](https://togithub.com/vitest-dev/vitest/issues/3834) [(711a6)](https://togithub.com/vitest-dev/vitest/commit/711a6249) - **watch**: - Clear screen on all terminals - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3661](https://togithub.com/vitest-dev/vitest/issues/3661) [(8bd26)](https://togithub.com/vitest-dev/vitest/commit/8bd26b01) ##### 🏎 Performance - Deprecate deps.registerNodeLoader - by [@sheremet-va](https://togithub.com/sheremet-va) [(7f45b)](https://togithub.com/vitest-dev/vitest/commit/7f45bf2d) - This option was introduced to support aliasing inside external packages. Please, use `deps.optimizer.web` instead. If you test Node.js applications, consider adding external packages to `server.deps.inline`. ##### [View changes on GitHub](https://togithub.com/vitest-dev/vitest/compare/v0.33.0...v0.34.0)Configuration
📅 Schedule: Branch creation - "before 12pm on Sunday" (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.
This PR has been generated by Mend Renovate. View repository job log here.