Open TheMikeyRoss opened 1 month ago
it's coming specifically from handleAuthRoutes
What is your environment, it is normal Node.js or other serverless platforms.
Logto is hosted in a Ubuntu 24 VPS and I'm trying to send api calls to it from a localhost in my local machine using windows 10. (regular node.js 18.x env)
Is this error happend in application or Logto itself?
in my node application in my localmachine in localhost (express.js)
If this error happend in SDK runtime, then could you please check the runtime of you Express.js app and see if "crypto" is available, or you can provide a repo that reproduces this error and I'll take a look.
Yes I have crypto installed and it's listed in my package.json
Usually you don't need to install "crypto" manually.
honestly it was already installed in my project before I started using logto
Please provide a minimal project that can reproduce the issue. This will help me better understand and assist you with your problem, for now, there is no enough context.
The project im using it it is a huge monorepo with 14 workspaces in it. I will try to put together a minimal reproduction
I'm encountering the same issue and it's coming from this file : node_modules\@logto\express\node_modules\@logto\node\lib\edge\generators.js
and it seems that for @logto/express package is not using the right version of @logto/node
here is what I see in generator.js , it's actually referring to crypto without importing it
Describe the bug
I followed the express.js tutorial and when I try to make a call to /logto/sign-in I get the following error
How to reproduce?
Context