tsd package problematic in serverless projects

[micheleangioni]

Dear team,
I've noticed that fairly recently this application included tsd into the dependencies of the project.

This has terrible consequences for our projects, because we use it in some AWS lambdas. As you probably know, the lambdas have size limits of the code they can contain. This includes the node_modules folder of course.

The problem is that tsd has an enormous size

and creates big problems when trying to deploy our lambdas in AWS, forcing us to use unpleasant workarounds.

Moving tsd to the devDependencies would already fix the problem, as it would be dropped when packaging the lambdas. If not possible, I really invite you to consider using a lighter alternative.

Thanks

[denysoblohin-okta]

Thanks for submitting this issue.
Internal ref: https://oktainc.atlassian.net/browse/OKTA-403207

[shuowu]

@micheleangioni Thanks for reporting the issue! The tsd module is used only for type testing, and it should belong to the devDependencies. Just wondering which version of okta-auth-js are you using, then we can release a patch for it.

[micheleangioni]

Hi @shuowu ,
thanks for the very fast answer :)

We include in our package.json the version 2.1.0 of @okta/jwt-verifier

It then brings this chain of dependencies:

[shuowu]

@micheleangioni @okta/jwt-verifier v2.2.0 which removed the dependency of @okta/configuration-valiadation has been released on npm. It should also resolves the tsd issue for your case.

Meanwhile, we are also working on move tsd to devDependencies in okta-auth-js. PR can be tracked #839

[micheleangioni]

Thank you very much @shuowu :)