This project implements an administration interface for the Instakittens project.
It is based on the awesome React-admin framework that lets you build admin web apps on top of REST/GraphQL APIs very rapidly.
It connects to the Instakittens JSON Server backend on port 3000.
Start the development server on port 3001:
npm run start
Run Jest unit tests in watch mode:
npm run test
End-to-end tests need a running development server on port 3001.
Run Puppeteer tests once:
npm run e2e
Run Puppeteer tests in watch mode:
npm run e2e:watch
Run Puppeteer Cucumber scenarios once:
npm run cucumber
Run Puppeteer Cucumber scenarios in watch mode:
npm run cucumber:watch
Run Playwright tests once:
npm run e2e-playwright
Run Playwright tests in watch mode:
npm run e2e-playwright:watch
Run Playwright Cucumber scenarios once:
npm run cucumber-playwright
Run Playwright Cucumber scenarios in watch mode:
npm run cucumber-playwright:watch
Run Cypress tests & scenarios once:
npm run cypress:run
Open Cypress GUI:
npm run cypress:open
Run TestCafé tests & scenarios once:
npm run testcafe
Run TestCafé tests & scenarios in watch mode:
npm run testcafe:watch
Run CodeceptJS tests & scenarios once:
npm run codeceptjs
Run CodeceptJS tests & scenarios in watch mode:
npm run codeceptjs:watch
This project was bootstrapped with Create React App along with the React-Admin dependencies.
create-react-app instakittens-react-admin
cd instakittens-react-admin
npm install react-admin ra-data-json-server prop-types
The app's default port 3000 has been changed to 3001 in the .env file.
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.