appToken is not read in socketMode @3.18.0 about bolt-js HOT 4 CLOSED

Ok, it works. So it did not work when I used bun even though my vars were loaded, when I changed to node the values were not loaded. I guess I cannot use bun for it. I don't know enough to understand why the different behaviour.

Thanks for your time and sorry for wasting it :).

from bolt-js.

Hi @headzik, thanks for asking the question! I've checked if your code example works for me, and I didn't see any issues with the SLACK_APP_TOKEN resolution using bolt-js 3.18.0. Probably there is still something wrong with your settings when running your app. I hope you'll find the cause out soon.

from bolt-js.

Thanks for the quick response. What could it be then? Why would it be settings of my app if it works in Python with the same token? What node version do you have?

from bolt-js.

What node version do you have?

I ran the code with Node 20 but it should not matter for this.

Why would it be settings of my app if it works in Python with the same token?

This is not an issue related to the validity of token. The token is not loaded in your Node.js app. As you can see here, the error can be thrown only when the appToken parameter is missing. You might set SLACK_APP_TOKEN variable in your shell session, but the data might not be loaded within your Node.js app for some reason (e.g., dotenv loads different set of data).

from bolt-js.