Skip to content

pgmanutd/employee-explorer

Repository files navigation

🎉 employee-explorer

Recursive employee explorer (multiway tree) using React along with duplicates removal.

Development

Checkout the repository

Open your favorite Terminal and run these commands:

cd employee-explorer

npm install

npm start

Available Scripts

In the project directory, you can run:

npm run start:server

Runs the express server in the development mode.
Open http://localhost:4000 to view it in the browser.

The server will restart if you make edits.

npm run start:client

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 start

Runs client and server scripts in parallel.

npm run lint

For running eslint on source code.

npm run format

For running prettier on source code.

npm test

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

npm run check

For running lint and test both.

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.