vite-tsconfig-paths VS okta-auth-js

Following suggestion in the issue, i looked at vite-tsconfig-paths which is even better because i already have configured vscode through typescript config:

Try this one. https://github.com/aleclarson/vite-tsconfig-paths

We need vite-tsconfig-paths in order to tell Vite how to resolve absolute paths from the tsconfig file. This way you can import modules like this:

You can use vite-tsconfig-paths on SvelteKit project. And it doesn't work, plese try delete generated folder for dev server like .svelte-kit.

We already have configured path aliases with webpack and tsconfig - so I wanted to keep that behavior. Luckily we have the vite-tsconfig-paths exactly for that. It worked well. I could also try using the alias for that.

hmm, I think I see why I'm confusing these two methods. In the context of using the okta-auth-js library.

Answer: This often happens when you're using a library with a umd bundle, where Vite expects an ESM bundle. This happened to me with okta-auth-js and the fix was to specifcally tell Vite to load the umd bundle in the Vite config file:

https://github.com/okta/okta-auth-js/issues/1194 might be related?

I've implemented auth using okta-react and okta-auth-js and everything works. However, I've now turned to the testing side using React Testing Library and I was wondering if anyone here has experience with using it with these Okta libraries? Do I have to mock an authenticated user?