A component library is helps designers save time and produce more consistent work. They are made up of designs, styles and pieces of software. source: Why Should You Use a React Component Library for your Project?
According to the website, "Chakra UI is a simple, modular and accessible component library that gives you the building blocks you need to build your React applications" In addition to React, the project documentation provides instructions for installing for getting started with React frameworks, including Next.js and Gatsby.js in the official documentation.
Examine what makes Chakra UI unique by:
- visiting the project documentation that compares and contrasts Chakra UI library with other popular UI and CSS frameworks including Theme UI, Tailwind CSS and Google's Material UI.
- Researching developer articles written on the subject.
This Readme assumes you've already created a Redux Application that you can install Chakra UI to be installed into.
If you are new to Redux, then follow the Getting started with React Redux tutorial listed in the official documentation.
The base of this project was built off of the official React Redux Tutorial: Using the connect API
Chakra-UI > Changing Color Mode
Chakra-UI > Creating your custom icons
Chakra-UI > Updating the theme config
🙏🏾 Thanks to the writers of the articles listed below. These resources helped me to understand the challenges.
- https://ui.dev/why-react-hooks/
- https://reactjs.org/docs/code-splitting.html
- https://reactjs.org/docs/hooks-intro.html#motivation
- https://reactjs.org/docs/hooks-overview.html
- https://www.telerik.com/kendo-react-ui/react-hooks-guide/
- Easy to understand React Hook recipes
"SharedArrayBuffers (SABs) can be used to construct high-resolution timers. High-resolution timers simplify Spectre attacks of cross-origin resources. To mitigate security risks across browsers, SharedArrayBuffers are gated behind cross-origin isolated contexts starting with Chrome 91 (May 2021). To continue using SharedArrayBuffers, please ensure that this page opts-into cross-origin isolation by setting Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy appropriately. Note that for each iframe, only the first issue is reported for performance reasons."
5/29 - Registered for SharedArrayBuffers in non-isolated
pages on Desktop platforms Trial to be implemented during production build and deployment
-
Making your website "cross-origin isolated" using COOP and COEP
-
SharedArrayBuffer updates in Android Chrome 88 and Desktop Chrome 92
In order to patch the deprecation and continue using SharedArrayBuffers, we need to input a Web Origin with an https, http, or chrome-extension prefix.
At this point, we're ready to deply v.0.0.1 of the application. Because it's a simple single page appliation that doesn't require database integration, to keep things simple with and scalable, I will be deploying to github pages.
Because I plan on adding more features and updating the UI, I will be deploying using ci/cd for continuous integation and access to scalable solutions offered in the github marketplace.
Github user gitname offers a useful guide for deploying create-react-app using the node package manager gh-pages. link
This project was bootstrapped with Create React App, using the Redux and Redux Toolkit template.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify