-
Notifications
You must be signed in to change notification settings - Fork 9
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
SyntaxError: Identifier 'self' has already been declared #4
Comments
Sorry, I didn't see your issue. I'll look into this as soon as I can |
Update: I was able to reproduce this issue, but only if the jellyfin-apiclient package is being updated to a higher version. I also noticed that there were some compile errors in the repo after pulling |
No, I just built from repo with |
I guess somehow this issue was resolved. There's another, when I'm trying to summon bot:
I'll try it in Docker now. |
Same in Docker:
Should I create another issue and close this since this error not related to old one? |
Do you mean a config.json?
You can build the container manually, but there is currently none published on a registry.
I think this is an upstream error. But it's hard to verify, because the code of this bot is incredibly messy. It's not ready for use at all, but I'll give it a shot and try to migrate all the previous code. |
Yeah, I accidentally skipped a few symbols :D
That's what I did.
Oh, alright! I can test it, because interested in this kind of bot. And there isn't any other kind of Jellyfin Music Bot than this non working code... |
That was exactly my problem too! The bot is honestly a bit cumbersome and there is a ton of stuff, I don't understand. My ultimate goal is to completely migrate everything, but it's hard, because the old project is outdated and a ton of discord.js API changed. |
btw, feel free to try out the nestjs branch. Use at your work risk though :) |
God, I forgot. Now I updated jellyfin-apiclient from fixed 1.7.0 to 1.10.0 and got another error:
And finally, because of orphaning original Jellyfin JS library and jellyfin-archive/jellyfin-apiclient-javascript#420 issue, I think they might be migrating to TypeScript actively now in https://github.com/jellyfin/jellyfin-sdk-typescript. |
Yes, I saw this issue too! I am using the new SDK in the |
I'll leave this issue opened for now, so people at least can see what's happening with project. |
Oh, or not, because of #6 |
Sure, no problem. You can subscribe to #6 so I can notify you for any changes if you want |
Cannot run app:
The text was updated successfully, but these errors were encountered: