Wildfire Tracker built with React and NASA API

This is project was made with help from a React tutorial by Traversy Media. I utilized this project as a way to get comfortable with using an API and React. This was also a good lesson on how to hide an API Key.

Table of contents

• Wildfire Tracker built with React and NASA API
  • Table of contents
    • Result
    • Screenshots
    • Links
    • Built with
• Getting Started with Create React App
  • Available Scripts
    • npm start
    • npm test
    • npm run build
    • npm run eject
  • Author

Result

Users should be able to:

• View the optimal layout for the site depending on their device's screen size.
• Click on any fire icon to view detailed information about that specific fire.

Screenshots

Links

• Solution URL: Github Repo
• Live Site URL: Live Site

Built with

• Create-React-App
• Google Maps API
• NASA EONet API
• Netlify
• Visual Studio Code
• Firefox Developer Edition

Getting Started with Create React App

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

npm start

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.

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.

Author

• Website - Ashley Yearicks
• Twitter - @jessarin5