See how is the weather around the world or nearby you, Wonderfully!
This project was bootstrapped with Create React App.
Take a look over how it was done: https://github.com/diegolameira/weather-nearby/projects/1
- CRA Scaffold
- Typescript
- Sass
- React
- Hooks, Context Api
- CSS Modules
- Reach Router
- Vercel (super fast static deploys CDN)
Duplicate the file on root called .env.sample
naming it as .env.local
(git will ignored it).
Set your env vars and your good to go.
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.
- Detail Screen
- Empty State Screens (List)
- Motions/Transitions/Animations
- Error Handlers
- Unit Tests
- Darkmode
- Improve Performance (web.dev/measure - lazyload map, etc)
- CodeSpliting
- PWA
CODE TIME PROJECT SUMMARY (Last updated on Mon, Nov 9th 5:25am)
weather-nearby : Nov 1st, 2020 to Nov 7th, 2020
Active code time : 7.8 hrs
Code time : 9.4 hrs
Keystrokes : 14,743
Kpm : 26
Lines added : 2,240
Lines deleted : 1,586
Characters added : 63,509
Characters deleted : 48,635