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.
Runs the electron app in the development mode.
The app 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.
Builds the app executable to the dist folder.\
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.
Runs the eslinter on all js, jsx, ts and, tsx files. All thanks to https://github.com/wesbos/eslint-config-wesbos
Source code typechecking based on the defined typescript rules from tsconfig.json
Format all the ts, js, tsx, jsx, css, json, md, html and, yml files. All thanks to https://github.com/wesbos/eslint-config-wesbos
On macOS, electron-builder expects two certificates, Developer ID Application and 3rd Party Mac Developer Application, to be present on the Keychain Access. In scenarios where a specification of the certificates are necessary, the env variables CSC_LINK and CSC_KEY_PASSWORD can be specified. To export both certificates into a single .p12 file, follow this guide.
On Windows, CSC_LINK and CSC_KEY_PASSWORD variables must be set. If the .p12 contains more than one certificate the field certificateSha1 must be provided on the package.json file. Currently, the Developer ID Application certificate are being used to sign the windows installer.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.