fix: replacing kyper token provider with a stub - #401
Conversation
|
Do we have a measure of how much this changes our bundle size? |
|
Will this be able to be imported to connections? Or will we have to do something similar over there? |
It should be negligible in either direction. It's mostly about not getting errors based on kyper token provider relying on specific versions of React, and allowing us to make the changes slowly over time. |
I would just do the same thing in the mx connect widget. I could export it from here, but pretty soon I'm going to import the package into the connect widget, and then it won't matter. |
codingLogan
left a comment
There was a problem hiding this comment.
An incremental step in the freedom direction feels good.
|
🎉 This PR is included in version 2.40.12 🎉 The release is available on: Your semantic-release bot 📦🚀 |
No description provided.