vite-plugin-svgr
okta-auth-js
vite-plugin-svgr | okta-auth-js | |
---|---|---|
4 | 5 | |
487 | 434 | |
- | 1.2% | |
7.2 | 7.5 | |
3 months ago | 8 days ago | |
TypeScript | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vite-plugin-svgr
-
Chrome Extension with React + CRXJS + Vite + Docker
If you want to use svg with React components, install vite-plugin-svgr.
-
Migrating from Create React App (CRA) to Vite
We need vite-plugin-svgr in order to import SVGs as React components. For example:
-
Repeating variable names for imports, types and switch. Got to be a better way!
If you're using Vite, then maybe try one of these: - https://github.com/pd4d10/vite-plugin-svgr - https://github.com/vbenjs/vite-plugin-svg-icons
-
Using Vite with React
Instead of webpack svgr - vite has a community plugin vite-plugin-svgr. Looking at its source code I can tell that it does the work as needed. In the future, I may want to add more SVGR options (currently for custom colors we use css currentColor property), so I may contribute it or create a similar plugin. NOTE: vite bundles the static svg in addition to assets even if you use vite-plugin-svgr. So many useless files will be generated. This is a minor issue that can be unnoticeable. I created a script for deleting those files (it has 0 impacts on the bundle because the client does not download those chunks).
okta-auth-js
-
OIDC / OpenID Connect - Single/Global Logout
hmm, I think I see why I'm confusing these two methods. In the context of using the okta-auth-js library.
-
Migrating from Create React App (CRA) to Vite
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:
-
Getting lots of 'Failed to execute 'postMessage' on 'BroadcastChannel': Channel is closed' errors
https://github.com/okta/okta-auth-js/issues/1194 might be related?
- [AskJS] Which JS OpenID Connect library to use in 2021?
-
Has anyone used Okta + react testing library?
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?
What are some alternatives?
webpack-bundle-analyzer - Webpack plugin and CLI utility that represents bundle content as convenient interactive zoomable treemap
node-openid-client - OpenID Certified™ Relying Party (OpenID Connect/OAuth 2.0 Client) implementation for Node.js.
svgr - Transform SVGs into React components 🦁
okta-react - Okta OIDC SDK for React
react-markdown - Markdown component for React
vite-tsconfig-paths - Support for TypeScript's path mapping in Vite
awesome-vite - ⚡️ A curated list of awesome things related to Vite.js
create-vite-app - Create a Vite-powered app in seconds!
rollup-plugin-visualizer - 📈⚖️ Visuallize your bundle
vite - Next generation frontend tooling. It's fast!
nivo - nivo provides a rich set of dataviz components, built on top of the awesome d3 and React libraries