Closed khteh closed 2 years ago
Hey there, can you provide a repro? It's been 2-3 issues you opened lately, all with partial copy/pasted code, but it's very time consuming to understand the problem and help you without a fully reproducible example I can launch and study by myself.
Hi, it is a private repository of a company I work for. I will see if I could provide a reproducible repo.
I'm having similar issues since updating vue from 3.2.31
to 3.2.32
or 3.2.33
.
@khteh could you check what version your vue is on to see if this might be related somehow?
@IlCallo we talked about this briefly in discord already. I'm getting the following error with the default jest test example when upating vue to 3.2.32
or 3.2.33
:
FAIL test/jest/__tests__/MyButton.spec.ts
● MyButton › correctly updates counter when button is pressed
TypeError: Cannot set properties of undefined (setting 'hasOwnProperty')
33 |
34 | it('correctly updates counter when button is pressed', async () => {
> 35 | const wrapper = shallowMount(MyButton);
| ^
36 | const { vm } = wrapper;
37 | const button = wrapper.findComponent(QBtn);
38 | await button.trigger('click');
at mount (node_modules/@vue/test-utils/dist/vue-test-utils.cjs.js:7925:27)
at shallowMount (node_modules/@vue/test-utils/dist/vue-test-utils.cjs.js:7934:12)
at test/jest/__tests__/MyButton.spec.ts:35:33
at test/jest/__tests__/MyButton.spec.ts:8:71
at Object.<anonymous>.__awaiter (test/jest/__tests__/MyButton.spec.ts:4:12)
at Object.<anonymous> (test/jest/__tests__/MyButton.spec.ts:34:69)
Edit: Found a related issue in the quasar core repo https://github.com/quasarframework/quasar/issues/13154
@squareloop1 that may be it, closing this as it's probably related to the Vue core problem
i am also facing the same problem i am also getting the same error
Unhandled Runtime Error
TypeError: Cannot read properties of undefined (reading 'mount')
Uncaught TypeError: Cannot read properties of undefined (reading 'mount')
at eval (QueryClientProvider.js:37:1)
at commitHookEffectListMount (react-dom.development.js:23150:1)
at commitPassiveMountOnFiber (react-dom.development.js:24926:1)
at commitPassiveMountEffects_complete (react-dom.development.js:24891:1)
at commitPassiveMountEffects_begin (react-dom.development.js:24878:1)
at commitPassiveMountEffects (react-dom.development.js:24866:1)
at flushPassiveEffectsImpl (react-dom.development.js:27039:1)
at flushPassiveEffects (react-dom.development.js:26984:1)
at eval (react-dom.development.js:26769:1)
at workLoop (scheduler.development.js:266:1)
at flushWork (scheduler.development.js:239:1)
at MessagePort.performWorkUntilDeadline (scheduler.development.js:533:1)
client.js:1 The above error occurred in the
at QueryClientProvider (webpack-internal:///./node_modules/react-query/es/react/QueryClientProvider.js:39:21)
at MyApp (webpack-internal:///./src/pages/_app.js:13:11)
at PathnameContextProviderAdapter (webpack-internal:///./node_modules/next/dist/shared/lib/router/adapters.js:80:11)
at ErrorBoundary (webpack-internal:///./node_modules/next/dist/compiled/@next/react-dev-overlay/dist/client.js:306:63)
at ReactDevOverlay (webpack-internal:///./node_modules/next/dist/compiled/@next/react-dev-overlay/dist/client.js:858:919)
at Container (webpack-internal:///./node_modules/next/dist/client/index.js:78:1)
at AppContainer (webpack-internal:///./node_modules/next/dist/client/index.js:182:11)
at Root (webpack-internal:///./node_modules/next/dist/client/index.js:372:11)
React will try to recreate this component tree from scratch using the error boundary you provided, ErrorBoundary. console.error @ client.js:1
Are you sure you're in the correct repo? This is a Quasar-related (Vue-based) library, your errors suggest you're using React
The error isn't even the same one
I have a Quasar 2 Vue 3 page which includes other custom components. This is my template:
Using
3.0.0-alpha.10
mount
runs into the following crash dump:Uing
shallowMount
does not have this crash dump but I am not able to.find()
anything insideq-page
. For example, thechai.expect
fails for the template shown above:Any advice and insight is appreciated.
Software version
OS: 21.10 Node: v17.8.0 NPM: 8.5.5 Any other software related to your bug:
What did you get as the error?
What were you expecting?
What steps did you take, to get the error?