Skip to content

Jiron/abschlussprojekt-modul294

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

22 Commits
 
 
 
 
 
 

Repository files navigation

Getting Started

To start off, you'll need to install all necessary npm packages inside of the react project (/frontend) as well as the backend node project (/backend).

To do this, make sure you have nodejs installed and then open cmd, navigate to one of the two folders, run

npm i

and do the same thing for the other folder to install all necessary packages.

Running The Application

To run the front-end environment, open cmd, navigate to /frontend and run

npm start

and to run the back-end environment, open another cmd, navigate to /backend and run

node server.js

This can also be done with nodemon when installed globally for easier editing.

Knowledge Base

Back-End Package Sources and Documentations

json-server

json-server-auth

jwt-decode

Front-End Package Sources and Documentations

Learn React

Specs

Tested on npm version 8.3.0 and nodejs version 16.3.0

Operating System: Windows 10 Pro, Version 21H2, Build 19044.1889

CPU: Intel(R) CORE(TM) i7-85500U CPU @ 1.80GHz 1.99Hz

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

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

npm run build fails to minify

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

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published