This is a follow-up to #1070.
We continue to experience errors about missing dependencies when using @descope/web-component or @descope/react-sdk without explicitly depending on oidc-client-ts.
After further investigation, I believe this is caused because we use Descope in a ClojureScript project, using shadow-cljs, which uses the Google Closure compiler under the hood.
shadow-cljs does not support dynamic imports, and from my understanding, this is in large part because Google Closure has limited support for them as well.
While we have solved the compiler errors for now by explicitly depending on oidc-client-ts, we do not make use of any OIDC functionality, and oidc-client-ts is the 5th largest package in our compiled output. It would be nice if we could use the Descope JS libraries without dynamic import or depending on OIDC explicitly.
I realize we are using a less common JS compiler, but any suggestions or improvements would be welcome :) Thanks!
This is a follow-up to #1070.
We continue to experience errors about missing dependencies when using
@descope/web-componentor@descope/react-sdkwithout explicitly depending onoidc-client-ts.After further investigation, I believe this is caused because we use Descope in a ClojureScript project, using shadow-cljs, which uses the Google Closure compiler under the hood.
shadow-cljsdoes not support dynamic imports, and from my understanding, this is in large part because Google Closure has limited support for them as well.While we have solved the compiler errors for now by explicitly depending on
oidc-client-ts, we do not make use of any OIDC functionality, andoidc-client-tsis the 5th largest package in our compiled output. It would be nice if we could use the Descope JS libraries without dynamic import or depending on OIDC explicitly.I realize we are using a less common JS compiler, but any suggestions or improvements would be welcome :) Thanks!