The jose dependency uses a number of nodejs native APIs that are not currently supported by default on Cloudflare. I found usage of "buffer" and "crypto" but there may be others
"buffer" can be supported on cloudflare if your worker has nodejs compatibility switched on, but only if the import includes the "node:" prefix, which jose does not currently do.
"crypto" is not supported at all, the only replacement would be the Web Crypto API
Effectively this means the v2 SDK cannot be used on Cloudflare in its current form, and the only way to use V2 Qstash from Cloudflare is to call the HTTP endpoints directly
The
jose
dependency uses a number of nodejs native APIs that are not currently supported by default on Cloudflare. I found usage of "buffer" and "crypto" but there may be others"buffer" can be supported on cloudflare if your worker has nodejs compatibility switched on, but only if the import includes the
"node:"
prefix, which jose does not currently do."crypto" is not supported at all, the only replacement would be the Web Crypto API
Effectively this means the v2 SDK cannot be used on Cloudflare in its current form, and the only way to use V2 Qstash from Cloudflare is to call the HTTP endpoints directly