-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: is config.global.components ignored by testing-lib? #279
Comments
Thanks for posting! I'm having the same issue - would love to see a fix to this. It seems that
Same setup works fine when using |
It looks like the problem is that when working with
As a workaround I've created an alias in // vite.config.ts
{
...
resolve: {
alias: [
{
find: '@vue/test-utils',
replacement: '/node_modules/@vue/test-utils/dist/vue-test-utils.cjs.js',
},
]
}
} There're probably better ways to to do this but ideally |
It would be really nice to fix this one. None of the setup files for vitest work without the workaround suggested by @purepear (using |
I'm having the same issue. Both |
i am facing the same issue with |
I'm having the same issue. config.global.plugins option doesn't work even with @purepear solution. vue-test-utils: 2.4.1 |
Global settings for Vue can be setup using // vitest.setup.ts
import Antd from 'ant-design-vue';
import { config } from '@vue/test-utils';
import '@testing-library/jest-dom';
config.global.plugins = [
Antd
] |
Describe the bug A clear and concise description of what the bug is.
According to the vue-test-utils documentation it is possible to register global stuff using
config.global.*
, so for instance with config.global.components = { HelloWorldComponent } you can make that component globally available. This works fine when using mount() from test-utils but fails when using render() from vue-testing-library (that is why I posted the bug here). Error message is such as:When adding the component directly to the global in the render() function it works, but not when setting it globally via config.global.
If this is intended that testing-library can only add the globals to the render function, it would mean I have to add the same global for every test (we have 300 tests right now). Then consider this as a feature request :-)
To Reproduce Steps to reproduce the behavior:
Here is a small reproduction project:
https://github.com/jonsalvas/testinglib-reproduce-config-global-issue
Expected behavior
All stuff registered using config.global is globally available in all components.
Screenshots
Related information:
@testing-library/vue
version: 6.5.1Vue
version: 3.2.25node
version: 17.8.0npm
(oryarn
) version: 8.5.5Relevant code or config (if any)
see reproduction project
Additional context
Initially I encountered the issue when upgrading @vue/test-utils from 2.0.0-rc.17 to 2.0.0-rc.21 so I was sure it was related to that. However when downgrading I was unable to make it work again. I assume my project was broken somehow.
The text was updated successfully, but these errors were encountered: