Any way to work around ERR_UNEXPECTED_PROXY_AUTH?

[galpt]

Got ERR_UNEXPECTED_PROXY_AUTH everytime I tried to use /setup.
Anyone's managed to work around that?

Also the README.md can probably explain something about that(?)
People might need an FAQ section as a reference.

[galpt]

Nvm.
It's caused by me mistakenly used the bot secret token instead of the oauth2 secret.

[Inrixia]

Ah, have you used typescript and cloudflare workers before?

When using typescript you have to compile/transpire aka build your code before publishing to the worker.

The two errors you got are typescript errors identifying issues with typing in your code, your edit should be showing you them while editing.

[galpt]

Nope, like I said, my 1st time trying to port my bot to cf workers. The bot was using Go before.
Maybe because of that, most features are causing the errors and I need to rebuilt them to work best with workers.

Guess I'll have to learn js & ts a bit more.
I'll try to google it more. Thanks for your time! @Inrixia

---

Actually this repo and your fork should work as expected.
I made a quick test feature last night and it seems only the feature that previously worked fine in Go needs to be adapted to JS/TS.

That being said, I'll wait until this repo supports InteractionResponseType.DeferredChannelMessageWithSource out of the box.

Right now trying to implement deferred reply isn't the most convenient way like using InteractionResponseType.ChannelMessageWithSource, and there aren't much examples of using defer reply with cf workers that I could find on google — at least not yet for this repo.

[Inrixia]

No problem, if you wanna discuss more you can add me on discord and I'd be happy to help explain things.

@Inrixia#0001

[Inrixia]

Or feel free to ask follow up questions on this discussion

[galpt]

Thanks @Inrixia .
Added you on discord!

[alvgaona]

Thanks, @galpt for the suggestion on improving the README file. I'll create an issue for that.