• Demo

• Getting Started

• What's inside?

• Architecture

• Learn More

• Motivation

• Technologies

• Challenges

• Roadmap

• Contribution

• License

• Contact

• Featured

• Acknowledgements

You need to have a OpenWeather Account, follow the instructions described here to create an account and grab an API key.

• Clone the repository

git clone https://github.com/iamsainikhil/weather-react.git

• Install the packages using the command npm install

• Create a .env file in the root directory of the project. Add the following properties in it:

  OPENWEATHER_API_KEY=<your OpenWeather API Key>
  

That's it! You can run the below available scripts to get up and running on the localhost. If you want to dive deeper into the codebase, I recommend you to check the architecture documentation to customize this application as your wish.

These instructions are very important to avoid the Blank Page issue when running the application on http://localhost:3000.

In the project directory, you can run:

vercel dev

Runs the app in the local development mode (npm run start) while serving serverless functions defined in the /api folder. Open [http://localhost:3000](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.

For more information, check the Vercel docs here

npm run start

Runs the app in the development mode. Open [http://localhost:3000](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.

npm test

Launches the test runner in the interactive watch mode. See the section about

running tests for more information.

npm run build

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.

npm run eject

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.

A quick look at the top-level files and directories in this weather-react project.

├── api
	├── address.js
	├── forecast.js
	├── hello.js
├── public
├── src
	├── components
	├──	containers
	├── context
	├── fonts
	├── sass
	├── styles
	├── tests
	├── utils
	├── App.js
	├── index.js
	├── serviceWorker.js
├── tailwind.config.js

1. api: This directory contain all of the code related to the back-end of the application.
   • <name>.js: This file serve as the serverless function which when deployed on Vercel will accept requests from the front-end application and return response.
2. public: This directory contain all the assets like images, icons, manifest (PWA), and favicons.
3. src: This directory contain all of the code related to what you see on the front-end of the application. src is a convention for “source code”.
   • components: This directory contain several React components with each component having an own directory.
   • containers: This directory contain several containers with each container wrapping many components defined in the above components directory. Each container have an own directory.
   • context: This directory contain context files with each file holding the logic related to the state shared between the containers & components.
   • fonts: This directory contain font files related to several font variations and formats.
   • sass: This directory contain the application styles written in scss grouped into several directories.
   • styles: This directory contain only two files main.css (styles used in development) and style.css (styles used in production).
   • tests: This directory contain test suites with each file containing several test cases testing a utility function or a component.
   • utils: This directory contain files with each file representing a utility function.
   • App.js: This is the main React component that is rendered in the DOM which contain the containers & components as well as routing.
   • index.js: This is the first file which gets run in the browser after starting the application. App.js component rendering as well as serviceworker registration process takes place in this file.
   • serviceWorker: This file contains the code related to registration/deregistration of a Service worker.
4. tailwind.config.js: This file contains the configuration related to tailwindcss.

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

For more info, check here: https://facebook.github.io/create-react-app/docs/code-splitting

For more info, check here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

For more info, check here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

For more info, check here: https://facebook.github.io/create-react-app/docs/advanced-configuration

For more info, check here: https://facebook.github.io/create-react-app/docs/deployment

For more info, check here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify

I started learning React in February 2020 and thought of putting knowledge into reality by developing an application. I am interested in building an application that is API resource-intensive to challenge me writing efficient code keeping performance, UX, maintainability, scalability, and optimization in mind.

There are so many weather-related applications out in the wild. So, the goal is to create a UI that is beautiful yet simple and effective for any user to use.

• This application is created with Create React App

• React (v16.12)

• Styling syntax was written in SCSS and using TailwindCSS

• There are bunch of scripts that run when you start application to compile scss to css

• First, I used the OpenWeather API to fetch the weather forecast data. However, 5-day forecast data was not reliable i.e. when a user on 14th March 2020 at 7:00 PM EST tries to fetch 5-day forecast data, will get forecast data starting 15th March 2020 at 12:00 AM UTC. This posed a big problem of categorizing 5-day data into individual days since the data is not always consistent and is based on UTC and not based on the user timezone. Finally, I switched to Dark Sky API which is more reliable and provides a robust data model. However, there is a limit of 1000 calls/day.

• Dark Sky API needs a proxy server to send and receive a response which was easy in the development stage using a browser extension like this to enable CORS in the browser. However, I can't ask every user to install this extension in their browser to check the weather forecast. So, I overcome this issue temporarily for now using the cors-anywhere library which you can get more info by checking here. However, I overcome the temporary solution and built a proxy server by deploying the Node.js API functions on the Vercel's serverless architecture and can be accessed here.

• Latest challenge I encountered is that Teleport API is temporarily shutdown and this led to broken autocomplete city search, and photos for favorited cities. Moreover, there is a tight coupling of code logic with this API. Now, I made a well thought highly scalable solution of using Algolia Places Rest API for fetching address based on city query as well as fetching city name based on latitude and longitude. I am very much happy about this change since it removed a lot of bad code and improved the application load times and performance.

  Note: The application UI/UX is not affected with this API change.

• Algolia Places shutdown it's Geocoding API on May 31st, 2022 which broke the address search autocomplete functionality in the app.

• Dark Sky got acquired by Apple and shut down it's API service at the end of 2021. At the same time, OpenWeather API introduced a new service One Call API 3.0 which is similar to Dark Sky API with more forecast features like hourly forecast for 48 hours, daily forecast for 8 days, national weather alerts, etc.

• Finally, replaced both Dark Sky & Algolia Places with just OpenWeather API for both weather forecast and reverse geocoding. However, address search autocomplete functionality is removed from the app.

• Build a proxy server using Express for Dark Sky API requests

• Convert to a TypeScript project

• Unit Testing

• Add documentation for components using Storybook

• Publish this project as an NPM package that can be consumed elsewhere.

• Open pull request with improvements.

• If you have any new idea, check the feature request template to create a request.

• If you found any issue or a bug, check the bug report template to create a report.

Have a look at the license file for details

Whether you’d like to discuss a project, ask me about my website or simply say “hello”, I’d love to hear from you.

Email: [email protected]

• React.js Examples

• Morioh

See the Acknowledgements page on the wiki for a list of Acknowledgements for Weather React codebase.