Suneil Nyamathi

I can reproduce this as well - here's a pretty minimal repo: ```json5 // package.json { "name": "example", "version": "1.0.0", "dependencies": { "@swc/cli": "^0.1.57", "@swc/core": "^1.3.11", "lodash": "^4.17.21" } }...

It may be possible to do so, but would you be able to add a `.stylelintignore` to ignore the generated Atomic CSS files? https://stylelint.io/user-guide/ignore-code/#files-entirely If we don't _need_ to add...

@kouhin the fix landed in undici v6.19.6 and Node 20.17 still uses undici v6.19.2 https://github.com/nodejs/undici/compare/v6.19.5...v6.19.6 https://github.com/nodejs/node/blob/v20.17.0/src/undici_version.h#L5 ----- edit: I've opened a PR to backport the fix to Node v20 https://github.com/nodejs/node/pull/54583

This is getting off topic for this issue, but the global fetch (https://nodejs.org/dist/latest-v20.x/docs/api/globals.html#fetch) which comes with node itself is different than adding a dependency on the npm package `undici` In...

This seems to be coming from https://github.com/vitest-dev/vitest/blob/ab5f8927065518e512ff2ccca48612a1206e43fe/packages/vite-node/src/client.ts#L370-L397 which is where the CJS scope variables are being provided to our ES Module.

Thanks for the response; I was hoping to migrate from to Vitest from Jest because Jest can't handle ES Modules ([issue](https://github.com/facebook/jest/issues/9430)). The project I'm testing is purely server side. Our...

@sheremet-va I did some work to determine when a module is ESM and remove the CJS scope variables in this branch: https://github.com/vitest-dev/vitest/compare/main...snyamathi:cjsCompat However, if the expectation is that Vitest is...

Understood, thanks for the explanation @sheremet-va It 100% makes sense that vitest would be primarily concerned with the needs of Vite and not meant as a general purpose test runner....