6460b23709
* configure the updater and some fix some macos tahoe css errors * enclosure for title_bar_style on Window build * those should have been added to the commit * test update to 0.6.0 * allow unused mut * update version in tauri.conf * fix versioned release draft * fix windows beforeBundle script * force app restart on update * fix release build * fix latest tag files * latest tag title * try testing for windows ARM * improve build workflow cleanup for cache * actually use the windows-11-arm runner * copy and bundle openssl items directly from runner * we actually need those files as placeholders for linters and unit tests * no need to rebuild assets when converting draft to published * fix verbosity * fix windows openssl dir * converting draft release to published should not run the build workflows * converting draft release to published should not run the build workflows * separate release draft build from publish * release dekstop dispatch * release dekstop dispatch * fix dylibs * undo fix_dylib change and attempt to handle restart on update * move restart exit code up * bump version to test updater restarting * windows updater signature * positional argument..? * arg is --password * try this for mac updater * add message to updater to inform users to start the app manually after update * add toast message for first API run * get windows to open the window after updating..? * cargo clippy * update package locks for vite * fix css thing * version bump for another test * bump for v 1 --------- Co-authored-by: deeleeramone <>
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