## What this teaches
How to courier.issueToken moved: use courier.authTokens.issueToken in v6.0.2+.
## The problem
Issue trycourier/courier-node#162 (closed, 5 comments): The reporter noticed the issueToken function had moved and there was no documentation or example showing its new location. A maintainer replied that the README would be updated, and confirmed that in v6.0.2 of the Node SDK the method lives at courier.authTokens.issueToken(...). The issue was then closed as supported.
## What worked (verified answer)
If you are looking for the courier.issueToken function in the Courier Node SDK and cannot find it, it moved. On v6.0.2 and later use courier.authTokens.issueToken(...) instead. The maintainers confirmed the new location while closing the issue, though the README update lagged behind, so do not rely on old examples. Note the maintainer's warning behind this too: without a scoped token from issueToken, new users end up passing their server key into client-side profile calls, which you should avoid. If your pinned version is older than v6.0.2, pin to v5.7.0 as an interim or upgrade to v6.0.2+.
## Source
gh:trycourier/courier-node#162 - https://github.com/trycourier/courier-node/issues/162