/react-minesweeper

react based minesweeper

Primary LanguageJavaScript

MineSweeper Built in React

Instructions

Write a minesweeper game with the following requirements using the Minefield component

  1. It should return a grid based on the rows/cols props in the render function.
  2. Each cell should handle a click event
  3. If the cell contains a mine, then the player should be notified they lost
  4. If the cell is adjacent to one or more mines, the the player should be notified how many mines are nearby
  5. If the cell is is not adjacent to a mine, then the grid should clear until and cell to an adjacent mine is found.
  6. If all cells except the mines are cleared then the player should be notified they won.
  7. Bonus: right clicking on a field should set a flag

This project was bootstrapped with Create React App.

Table of Contents

Folder Structure

After creation, your project should look like this:

my-app/
  README.md
  node_modules/
  package.json
  public/
    index.html
    favicon.ico
  src/
    App.css
    App.js
    App.test.js
    index.css
    index.js
    logo.svg
    Minefield.js

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.