This message was deleted.
# cloud
s
This message was deleted.
d
can you link me to the example you are trying?
l
livekit 101 :)) … using remix 1.3.4
d
CC: @acoustic-engineer-41666
p
I don’t have experience with remix, but there’s two related issues on their GH, mentioning workaround/how to deal with ESM modules. https://github.com/remix-run/remix/issues/1283 https://github.com/remix-run/remix/issues/109
l
maybe this will be helpful tu anyone but when starting the remix project and choosing vercel (or similar) as the deployment target u might have the error i got … but with cloudflare pages the error did not appear
got happy too soon … livekit-server-sdk depends on crypto which does not work on cloudflare pages … so u won’t be able to generate tokens
d
hmm, CF pages doesn't support Node crypto?
p
l
thank you @polite-kilobyte-67570
guyz is this the normal payload of a jwt?
Copy code
access token AccessToken {
  apiKey: 'api-key',
  apiSecret: 'secret-key',
  grants: {
    video: {
      roomJoin: true,
      room: 'name-of-room',
      canPublish: true,
      canSubscribe: true
    }
  },
  identity: 'user-name',
  ttl: 21600
}
i am assuming the jwt gets verfied using the apiSecret … if that is the case why would the apiSecret be in the payload?
just saw that u do not include it in the jwt … nvmd 😄