Portfolio_Ryan made with javascript and React. then converted to Typescript.
This application uses a root at it html that passes to the index.tsx file. the index.tsx is rendering a function that is imported from the App.tsx file. The App.tsx file is using 3 paths through the components files that is being through the Navigation.tsx file as a function that navigates the pages when clicked. The images were selected through a actual URL.
https://ryanpaezportfolio.herokuapp.com/
"@testing-library/jest-dom": "^5.16.4", "@testing-library/react": "^13.3.0", "@testing-library/user-event": "^13.5.0", "@types/jest": "^28.1.6", "@types/lodash": "^4.14.182", "nodemon": "^2.0.19", "react": "^18.2.0", "react-dom": "^18.2.0", "react-router-dom": "^6.3.0", "react-scripts": "^5.0.1", "source-map-loader": "^4.0.0", "ts-loader": "^9.3.1", "web-vitals": "^2.1.4", "webpack": "^5.74.0"
If issue occurs, it is likely because of the conversion of typescript. The biggest issue was to find where the home page was to when npm start. Under package.json "homepage": "https://github.com". I was not set initially set up with this route and took me a while to figure out why is is using https:// vs src . I still do not know exactly why because it started doing this when TypeScript was injected.
No API's were needed for the profile page. Just wanted to do a little FrontEnd with CSS.
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may 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