➡ Project Technical Characteristics
This project was created with Create React App.
However, it is now bootstrapped by netlify cli.
Meaning that running one command (netlify dev) will start both:
- the backend (
netlify functionsliving inside the[root]/backend/directory) - the frontend (a
create-react-appapp living inside the[root]/src/directory)
This means that both backend AND frontend logs will print within the same console. No need to open a separate terminal windows for each, which is great !
This project can be locally ran on your dev machine.
Here's how :
- clone this repository on your local machine
- from the root directory, run the following commands in the terminal:
- yarn
- netlify login
- netlify status
- netlify link
- Choose option: `use current git remote origin (https://github.com/boostup/react-spotify-clone-app)`
- netlify dev
Error: Unable to open browser automatically: Command failed: wslpath \System32\WindowsPowerShell\v1.0\powershell.exe wslpath: \System32\WindowsPowerShell\v1.0\powershell.exe
- restart the terminal (by closing it and opening it again for example).
- run
netlify devagain - the message should no longer appear, as it actually managed to open the browser window which failed previously
- create a file called exactly:
.env.development - grab all variables stored in netlify
- replace all instances of
jovial-mccarthy-6875cf.netlify.appwithlocalhost:8888 - save the file at root directory level (so same level as other directories such as
srcorbackend) - run
netlify dev ◈ Injected .env.development file env var: APP_DOMAINfor example will confirm that it work, as it would otherwise show:◈ Injected build setting env var: APP_DOMAIN=> pay attention to the difference :Injected .env.developmentvsInjected buildportions
This project was bootstrapped with Create React App.
In the project directory, you can run:
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.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
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.
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.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify