Skip to content

OAXP/path-find-visualizer

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

14 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Path Finder Algorithm Visualizer

I created this project to learn more about path finding algorithms and how can they be shown visually using React JS.

Preview

image

Buttons

Wall

image By clicking on this button you activate the "place walls" mode and you can place walls anywhere on the grid.

Start Point

image By clicking on this button you activate the "place start point" mode and you can place the start point anywhere on the grid.

End Point

image By clicking on this button you activate the "place end point" mode and you can place the end point anywhere on the grid.

Reset

image Click to reset the grid to the initial state.

Random Maze Generator

image Click to generate a random maze. You have to place the starting and ending point after the generation.

Start Algo

image Start looking for a path using the algorithm chosen in the dropdown.

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 your browser.

The page will reload when you make changes.
You may 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.