There isn’t an example for that. But you can find the component that’s overridable and “closest” to the field. And replace that

To replace it, you can copy the code from the lib for the component and make mods to that as per your choice.

Unfortunately, this stuff isn’t optimised at the moment from an overriding point of view, but it’s certainly possible to do

ok, thanks a lot 👍

👍

Lmk if you got it to work as per your liking 🙂

so, I have a stage name

/dev

but since I have a custom domain name, the stage is already mapped to this custom domain name. so, I don't have the

apiGatewayPath

property set up.

I see. So your

apiDomain

value in the

appInfo

config is your custom domain?

yes. which includes the

/dev

stage.

oh i see. the

apiDomain

should not contain any path

so when you query your API via postman, whats the URL you use? (Can you give the full URL including the path here?)

You should try the appInfo config like:

{
  ...
  apiDomain: "YOUR CUSTOM API DOMAIN WITHOUT A PATH",
  apiGatewayPath: "/dev"
}

And see if this works. This assumes that you query "https://yourcustomdomain.com/dev/auth/signup POST" via postman. If on the other hand, your custom domain points to /dev/*, then you don't need the

apiGatewayPath

so, if I try to hit my

api.tonka.com

it points to

api.awsapigateway.com/dev

, which works but if I try to hit

api.tonka.com/dev

then that breaks because it tries to hit

api.awsapigateway.com/dev/dev

which doesn't exist, right. so, in the config I have only

apiDomain

with

api.tonka.com

and I have no

apiGatewayPath

set cause that will break.

hmm. okay. this makes sense

let me see what else I can do to help you debug this

Can you please provide some handler to the

middleware()

like so:

module.exports.handler = middy(middleware((event, context, callback) => {
  console.log("middleware did not find any route to handle...");
})).use(cors({
    origin: getBackendConfig().appInfo.websiteDomain,
    credentials: true,
    headers: ["Content-Type", ...supertokens.getAllCORSHeaders()].join(", "),
    methods: "OPTIONS,POST,GET,PUT,DELETE"
}));

And see if the message "middleware did not find any route to handle..." get's printed out or not.

I cannot even add

event,context,callback

as arguments to the

middleware

function. the type you have exposed is

export declare const middleware: () => import("aws-lambda").Handler<any, any>;

Ahh.. the types are incorrect (will fix). But you can add a handler in it

okay, added the snippet above in my Auth Lambda function and I do not see the comment logged out...

hmmmmm

but you are sure that the lambda is being called..

okay i think @User will be the best person to help you out for this as he made the AWS lambda integration. He will reply in a few hours.

is it possible for you to edit the supertokens-node package in the node_modules folder and run that in the AWS lambda? We can debug the issue by adding a few console logs in the package itself.

hmm, that's a good one. okay. I will do some tests tonight.

You wanna add console logs here: 1) https://github.com/supertokens/supertokens-node/blob/master/lib/build/framework/awsLambda/framework.js#L228. If this is not called, it means the middleware is not running. Which will be very, very weird 2) You want to print out the value of

result

here: https://github.com/supertokens/supertokens-node/blob/master/lib/build/framework/awsLambda/framework.js#L232 3) https://github.com/supertokens/supertokens-node/blob/master/lib/build/supertokens.js#L142. Add a random console log here as well (before the

path

variable is created). If (1) is getting printed out, then this one should as well. 4) Add a random console log here: https://github.com/supertokens/supertokens-node/blob/master/lib/build/supertokens.js#L150 (before

requestRID

is created). If this doesn't get printed out, it means that the middleware is not handling requests cause it thinks the request path is not something it should handle. In this case, you want to see the value of this

path

variable: https://github.com/supertokens/supertokens-node/blob/master/lib/build/supertokens.js#L142 If you want, we can even get on a call to do this together so that we can find the issue more quickly. Otherwise lmk about the results of the above please 🙂

@rp okay, maybe I got it. so, all of the 4 locations you wanted me to put some logs in actually returned logs. not a problem. but then I continued logging from within ST and in the

this.errorHandler

, right before

if (error_1.default.isErrorFromSuperTokens(err)) {

I logged the error object just to check whether any errors are thrown. well, there is an error. 😄

ST err: Error: The running SuperTokens core version is not compatible with this NodeJS SDK. Please visit https://supertokens.io/docs/community/compatibility to find the right versions
    at Querier.<anonymous> (/var/task/node_modules/supertokens-node/lib/build/querier.js:88:27)

ohhh i see!

however, when I go to

https://supertokens.io/docs/community/compatibility

I got an empty web page...

😄