New project with Oruga modal example not working

[ghost]

Hello,

I just installed vscode with vue 3 and oruga and created a new vue project.

I literally just copied the modal example from Oruga and it does not work, the text "Lorem ipsum..." is displayed directly with no buttons.

On firefox console i see:

[Vue warn]: resolveComponent can only be used in render() or setup(). 2 runtime-core.esm-bundler.js:38

[Vue warn]: Unhandled error during execution of render function
at
at
at

[Vue warn]: Unhandled error during execution of render function
at
at
at runtime-core.esm-bundler.js:38

[Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://new-issue.vuejs.org/?repo=vuejs/core
at
at
at

how can i know what am i doing wrong?

[liulinboyi]

Please provide a minimum reproduction, thanks! need more info.

[ghost]

Okay! Here it goes:

-> i type "vue create newproject" in vscode (Vue3+babel+eslint)
-> in the new created project i go to main.js and add the following two lines:
----> import Oruga from '@oruga-ui/oruga-next'
----> import '@oruga-ui/oruga-next/dist/oruga.css'
-> Open the component HelloWorld.vue and copy the code from the base modal in:
----> https://oruga.io/components/modal.html
-> type in terminal: npm run serve
-> open localhost:8080 and verify modal is not working, the text is displayed without clicking anywhere. Also errors appear on dev console:

[Vue warn]: Failed to resolve component: o-button
If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.
at
at runtime-core.esm-bundler.js:38

[Vue warn]: Failed to resolve component: o-modal
If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.
at
at

[Justineo]

You need to register these components before you use them in your template. https://oruga.io/documentation/#setup

[ghost]

Finally solved this!!

I completely uninstalled vscode (removing appdata folders too). After reinstalling and redownloading npm components it worked!!!

Dont know what was wrong tho...

Thank you all!