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
When running the production build of our app using okta-auth-js and okta-react the okta license is added into the js file 196 times, adding 122kb in size.
Reproduction Steps?
Using okta-auth-js and okta-react run a production build in vite with minify set to true
In the output .js file should be a comment for every okta function.
This would be trivial to strip out as part of our build, but we're keen not to break any licensing laws and it would be good to have this potentially fixed on oktas side.
If this is not fixable on your side then it's important to know wether on not we can remove all but 1 of these licensing comments.
The text was updated successfully, but these errors were encountered:
Thanks for pointing this out. We'll work on a fix on our side
In the meantime, you could try importing only the core bundle, rather than the default bundle (which includes everything in authjs). The core bundle should save a bit of bloat
Thanks for pointing this out. We'll work on a fix on our side
In the meantime, you could try importing only the core bundle, rather than the default bundle (which includes everything in authjs). The core bundle should save a bit of bloat
Describe the bug
When running the production build of our app using
okta-auth-js
andokta-react
the okta license is added into the js file 196 times, adding 122kb in size.Reproduction Steps?
Using
okta-auth-js
andokta-react
run a production build in vite with minify set totrue
In the output .js file should be a comment for every okta function.
SDK Versions
System:
OS: macOS 13.6.2
CPU: (12) arm64 Apple M2 Pro
Memory: 4.23 GB / 32.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.19.0 - ~/.nvm/versions/node/v18.19.0/bin/node
Yarn: 1.22.11 - ~/.nvm/versions/node/v18.19.0/bin/yarn
npm: 10.2.3 - ~/.nvm/versions/node/v18.19.0/bin/npm
Browsers:
Chrome: 120.0.6099.216
Safari: 17.2
npmPackages:
@okta/okta-auth-js: ^7.5.0 => 7.5.0
@okta/okta-react: ^6.7.0 => 6.7.0
Additional Information?
This would be trivial to strip out as part of our build, but we're keen not to break any licensing laws and it would be good to have this potentially fixed on oktas side.
If this is not fixable on your side then it's important to know wether on not we can remove all but 1 of these licensing comments.
The text was updated successfully, but these errors were encountered: