-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Vue 3 Object(...) is not a function #528
Comments
Are you sure you're using alpha5? Newest I can found is alpha4. And there everything is working for me using @socket Decorator. |
Okay, I need to correct my comment. Got the warning on compile-time too. Remembered that there were some breaking changes in alpha stated here #489 (comment) |
@ReazerDev In v5 decorator is supposed to be imported from the sub-path: import { Socket } from 'vue-socket.io-extended' // v4
import Socket from 'vue-socket.io-extended/decorator' // v5 could you check whether it works this way? |
Nope I've been using alpha-4. I'm updating to alpha-5 now. |
@ReazerDev That's weird. How are use transpiling TS in vue files? With typescript or babel? Or maybe something more cutting edge, e.g. esbuild? |
I'm using babel |
I just updated to alpha.5 and it's working for me. Think I'm using babel too. |
I'll push the repo to Github and post a link here, once I'm home👍 |
@ReazerDev got your repo working. Just updated the dependencies to the newest ones. Especially the ones with "@vue/...". |
Wait I think I just now realised, that you mean, that everything is working and not that you got my repo working and are starting to look what causes my issue? |
No. I meant that I got your repo working by updating the dependencies. You need to update the dependencies with "@vue/..." to get your repo working. |
Hi, I'm using alpha5 and when I'm trying to use the Socket Decorator I get a TypeError in the function beneath it:
Object(...) is not a function
.When I remove the Decorator, the TypeError is gone.
Also when running npm run serve, I get a warning:
The text was updated successfully, but these errors were encountered: