Pathfinding Task

A React pathfinding web app. 🐈

🔩

• Styled components.
• Responsive design.
• An interesting React hook for web workers useWorker.
• Bootstrapped with Create React App.
• BFS.

Was built and served to see whether everything works in production.

Things Not Finished & Thoughts

• Two possible algorithms.
• Details in the LevelsData (data screen) component.

Was interesting to use styled-components after styled-system. Unfortunately I ran out of time for the unfinished parts of the task. Things to think about:

• For CRAs, figure out how to use craco and worker-plugin for building worker scripts with easier importing of node modules. This would allow importing PathFinding.js (for the algorithms) into workers. I think Next.js offers a custom webpack configuration out of the box.
• Possibly read more about Redux.
• Do runners (the algos) have to actually run twice since their activation, in order to complitely follow the rules of the task (because of the way blocks have to be placed, randomly yet always checking whether or not if there could be a possible path through the grid);

.....

CRA generated README part is below.

Available Scripts

In the project directory, you can run:

yarn 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.

yarn test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

yarn 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.

yarn 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.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Code Splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

Analyzing the Bundle Size

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

Making a Progressive Web App

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

Advanced Configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

Deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

yarn build fails to minify

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify