- Designing database diagrams.
- Service, Module, Modulator
- Connect to the database, describe the data schema
- REST API, DTO
- File upload, static distribution, FileService
- CORS, completion of server development
-
Creation of the NEXT project
-
Player location
-
Page with step-by-step track creation
-
File upload component
-
Player logic, Redux connection, next Redux wrapper
-
Typing PlayerReducer
-
Custom hooks useActions, useTypedSelector
-
Action creators
-
Working with the Audio object in the browser, playing a track
-
Custom hook using Input
-
Creating a track, requesting a server, sending files
-
SEO optimization, title, title, meta
-
Search for tracks, optimize search queries
- There is a main AppModule in which all other modules are connected
- The module is an isolated environment, allowing you to quickly navigate and develop the application
- Each module has its own services, circuits, controllers
- The controllers work with requests, responses, and the client-server component
- Diagrams describe the data with which interaction takes place.
- In the DTO we describe the objects that are expected as input in some functions in the controllers
- As a result, all this is connected to the Web Module, which was later defined as the main one when the application was launched in the main file
- Cors for sending requests from the browser
- React
- Redux
- Hooks
- Cors
- Typescript
- Rest-api
- Scss
- Nest
- Seo-optimization
- Next
- Useactions
- Axios-react
// first install all necessary dependencies
npm i
// next run
npm start