You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We encountered an issue with version 4.5.1 of the library where the named export 'IDVClient' is not found.
import {
IDVClient,
} from 'yoti';
const idvClient = new IDVClient(
YOTI_CLIENT_SDK_ID,
YOTI_PEM
);
Our server automatically updates to the latest version of the 'yoti' library upon deployment. As a result, we encountered this issue after deploying version 4.5.1. Downgrading to version 4.5.0 temporarily resolved the issue.
PS: we are not using any TypeScript.
The text was updated successfully, but these errors were encountered:
Apologies for the delay.
Could you please tell use a bit more about your project setup.
As per the root cause of your issue, I am not so sure... the version 4.5.1 is only introducing the TS support and generates a side /types folder, which should not influence your existing setup, which does not rely on TS.
In the latest version, we have not introduced code change per se, and the IDVClient is still exported as before.
We tested the changes via the examples in the project, yet, granted this is a bit old school as these use require, see the code in examples/idv/src/controllers/use-cases.
Then, we also tested in some internal Typescript project, without noticing any problem.
Therefore, we would need to know a bit more about your project setup, how come you are using import but no Typescript, you are using ESM? or transpile your files?
Then, could you please check if using the following pattern would solve it:
We encountered an issue with version 4.5.1 of the library where the named export 'IDVClient' is not found.
Our server automatically updates to the latest version of the 'yoti' library upon deployment. As a result, we encountered this issue after deploying version 4.5.1. Downgrading to version 4.5.0 temporarily resolved the issue.
PS: we are not using any TypeScript.
The text was updated successfully, but these errors were encountered: