-
-
Notifications
You must be signed in to change notification settings - Fork 41
Conversation
Updated dependencies detected. Learn more about Socket for GitHub ↗︎
|
36805e9
to
d8ff8a0
Compare
58b046d
to
a489652
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
@sheremet-va Do you have any idea how we can get the |
80eb116
to
13ea9b3
Compare
|
Strangely, even though we've made that change in this PR, it still fails to run. (In other words, it's not behaving the same as |
What I'm seeing in the PR is that Vite resolves Anyway, publishing CJS entry seems pointless when you import from |
Checking when removing CJS builds, the issue is that But even when patching vitest, it doesn't solve the issue. We still end up with the following error:
Note that this is a regression in this version of vitest - it's not replicable with the exact same code in 0.33. |
An update to environments is released in 0.34.4 |
a3fdfcc
to
175d23b
Compare
@sheremet-va We now have a new issue with
Checking the vite node context, we have this: {
__filename: '/Users/daniel/code/nuxt-vitest/playground/debug',
__dirname: '/Users/daniel/code/nuxt-vitest/playground'
} These seem like the wrong results for the transform request, but I could be wrong. |
Should be fixed by: vitest-dev/vitest#4196 I am a bit surprised it works like this, looks like a potential performance optimization. |
@sheremet-va I really appreciate all your help on this ❤️ |
Fix is released in 0.34.6 |
The error now is caused by multiple instances of Vue. Tried with In I am able to fix most of the tests with (still some failing with other errors): test: {
deps: {
optimizer: {
web: {
enabled: false
}
}
},
} I am a bit rusted with Vitest, I guess @sheremet-va might have a better context? |
I also found that, in |
Even though the environment file is loaded in the same scope as your tests, it is now always processed with I would recommend rewriting the environment to be environment agnostic (don't rely on imports because they are environment-specific), to be honest. To support VM (which is faster and might be the direction Vitest takes in the future), you would need to rewrite it with a similar notion in mind. |
@danielroe @antfu It's a bit hard to grasp the scope of changes necessary here, is there anything we could do to help this along? 😄 |
This PR contains the following updates:
0.33.0
->0.34.1
^0.33.0
->^0.34.0
10.5.2
->10.8.0
0.33.0
->0.34.1
^0.24.5 || ^0.26.0 || ^0.27.0 || ^0.28.0 || ^0.29.0 || ^0.30.0 || ^0.33.0
->^0.24.5 || ^0.26.0 || ^0.27.0 || ^0.28.0 || ^0.29.0 || ^0.30.0 || ^0.33.0 || ^0.34.0
Release Notes
vitest-dev/vitest (@vitest/coverage-v8)
v0.34.1
Compare Source
🐞 Bug Fixes
--experimental-vm-worker-memory-limit
totinypool
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3856 (3c67a)View changes on GitHub
v0.34.0
Compare Source
🚨 Breaking Changes
transformMode
is now moved toserver.transformMode
. This option is highly discouraged to use. If you need to change the transform mode, use the new optiontestTransformMode
instead to control the mode based on the running test, not the current file path. By default, tests withjsdom
orhappy-dom
useweb
transform mode, and tests usingnode
oredge
environment usessr
mode. If you have a custom environment, it should providetransformMode
property.coverage.reportOnFailure
by default - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3615 (0c6f6)@vitest/coverage-c8
package - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3614 (a90d6)@vitest/coverage-c8
is no longer supported. Please, use@vitest/coverage-v8
instead.experimentalVmThreads
pool to run your tests using VM Sandboxes environment. Make sure you understand all pitfalls of this pool before opening an issue.server
option - by @fenghan34 and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3725 (dc4fa)deps.
options are now moved toserver.deps
with a deprecation warning. Please, consider usingdeps.optimizer
instead ofdeps.inline
/deps.external
. Ideally, we would like to move away from usingserver.deps.inline
altogether.vite-node index.ts --watch
, you now have to dovite-node --watch index.ts
.deps.optimizer
is now enabled by default. This means that Vitest will bundle specified dependencies before running your tests. This field inherits options fromoptimizeDeps
andssr.optimizeDeps
which are populated by other plugins (like, Svelte).🚀 Features
describe.sequential
- by @fenghan34 and @dammy001 in https://github.com/vitest-dev/vitest/issues/3771 (86934)--related --watch
reruns non-affected tests if they were changed during a run - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3844 (c9aea)🐞 Bug Fixes
defineConfig
type from vite - by @sodatea in https://github.com/vitest-dev/vitest/issues/3804 (9c8e3)toStrictEqual
- by @Dunqing (52aef)istanbul-lib-instrument
to v6 to fix vulnerable dependency - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3814 (f3bd9)🏎 Performance
deps.optimizer.web
instead. If you test Node.js applications, consider adding external packages toserver.deps.inline
.View changes on GitHub
capricorn86/happy-dom (happy-dom)
v10.8.0
Compare Source
👷♂️ Patch fixes
HTMLButtonElement.attributes.removeNamedItem()
. (#1010)Thank you @maxmilton for your contribution!
v10.7.0
Compare Source
🎨 Features
Element.scrollHeight
. The property will just return "0" for now. (#991)Thank you @lukaselmer for your contribution!
v10.6.3
Compare Source
👷♂️ Patch fixes
CSSStyleDeclaration
. (#1004)Thank you @AlexisTessier for your contribution!
v10.6.2
Compare Source
v10.6.1
Compare Source
👷♂️ Patch fixes
HTMLButtonElement.labels
,HTMLInputElement.labels
,HTMLSelectElement.labels
andHTMLTextAreaElement.labels
. It will now also return labels associated by being a parent. (#988)Thank you @joshkel for your contribution!
v10.6.0
Compare Source
🎨 Features
HTMLLabelElement.control
. It will now find child control elements that are deeper than one level. (#530)Thank you @joshkel for your contribution!
v10.5.3
Compare Source
👷♂️ Patch fixes
NamedNodeMap
, which is used by theElement.attributes
property. It will now reflect any changes done to it on the Element itself. (#728)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.