fix: use happy-dom/jsdom types for envionmentOptions#7795
fix: use happy-dom/jsdom types for envionmentOptions#7795sheremet-va merged 5 commits intovitest-dev:mainfrom
envionmentOptions#7795Conversation
✅ Deploy Preview for vitest-dev ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
@vitest/browser
@vitest/coverage-istanbul
@vitest/coverage-v8
@vitest/expect
@vitest/mocker
@vitest/pretty-format
@vitest/runner
@vitest/snapshot
@vitest/ui
@vitest/spy
@vitest/utils
vite-node
vitest
@vitest/web-worker
@vitest/ws-client
commit: |
v3.1.2 🐞 Bug Fixes Add global chai variable in vitest/globals (fix: #7474) - by @Jay-Karia in vitest-dev/vitest#7771 and vitest-dev/vitest#7474 (d9297) Prevent modifying test.exclude when same object passed in coverage.exclude - by @AriPerkkio in vitest-dev/vitest#7774 (c3751) Fix already hoisted mock - by @hi-ogawa in vitest-dev/vitest#7815 (773b1) Fix test.scoped inheritance - by @hi-ogawa in vitest-dev/vitest#7814 (db6c3) Remove pointer-events-none after resizing the left panel - by @alexprudhomme in vitest-dev/vitest#7811 (a7e77) Default to run mode when stdin is not a TTY - by @kentonv, @hi-ogawa and @sheremet-va in vitest-dev/vitest#7673 (6358f) Use happy-dom/jsdom types for envionmentOptions - by @hi-ogawa in vitest-dev/vitest#7795 (67430) browser: Fix transform error before browser server initialization - by @hi-ogawa in vitest-dev/vitest#7783 (5f762) Fix mocking from outside of root - by @hi-ogawa in vitest-dev/vitest#7789 (03f55) Scale iframe for non ui case - by @hi-ogawa in vitest-dev/vitest#6512 (c3374) coverage: await profiler calls - by @AriPerkkio in vitest-dev/vitest#7763 (795a6) Expose profiling timers - by @AriPerkkio in vitest-dev/vitest#7820 (5652b) deps: Update all non-major dependencies - in vitest-dev/vitest#7765 (7c3df) Update all non-major dependencies - in vitest-dev/vitest#7831 (15701) runner: Correctly call test hooks and teardown functions - by @sheremet-va in vitest-dev/vitest#7775 (3c00c) Show stacktrace on test timeout error - by @hi-ogawa in vitest-dev/vitest#7799 (df33b) ui: Load panel sizes from storage on initial load - by @userquin in vitest-dev/vitest#7265 (6555d) vite-node: Named export should overwrite export all - by @hi-ogawa in vitest-dev/vitest#7846 (5ba0d) Add ERR_MODULE_NOT_FOUND code error if module cannot be loaded - by @sheremet-va in vitest-dev/vitest#7776 (f9eac) 🏎 Performance browser: Improve browser parallelisation - by @sheremet-va in vitest-dev/vitest#7665 (816a5)
|
This introduced a regression for us. Now vitest pulls in We can't really upgrade to the latest version of vitest due to this. Not sure if there is any workaround? |
Can you provide a reproduction (what's different before and after this chanege)? I'm not entirely sure how this happens exactly and whether this is a bad behavior. If you use jsdom or happy-dom and you also import
I think you can use tsconfig // tsconfig.json
{
"compilerOptions": {
"paths": {
"happy-dom": ["./happy-dom-patch.ts"],
"jsdom": ["./jsdom-patch.ts"],
}
}
}
// happy-dom-patch.ts
export {}
// jsdom-patch.ts
export {} |
|
I'm not using jsdom or happy dom, it's a cloudflare worker package inside a mono repo. For some reason I see DOM packages being pulled in. Not sure if it's related to our mono repo setup. |
|
@skovhus I think the workaround I mentioned above should be fine if you are not using |
Description
Using the same idea as vitejs/vite#18460.
It looks like happy-dom's dts includes invalid types (though largely completion should work), so it's breaking
test/dts-configwhich tests withskipLibCheck: false.For now, I add a hack in
test/dts-xxxto not pick up this error.Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
pnpm-lock.yamlunless you introduce a new test example.Tests
pnpm test:ci.Documentation
pnpm run docscommand.Changesets
feat:,fix:,perf:,docs:, orchore:.