Bump the npm_and_yarn group across 1 directory with 3 updates

.cursorrules

@@ -0,0 +1,86 @@
+always think before action. be precise
+its preferable to implement unittest for the section you are working on.
+properly comment your algorithm and write cleancode
+think deeply when debugging before action
+when you debug and find you see that you need a tool to fix the issue, start implementing it and save it in tools folder and use virtual environment to use it.
+
+# React Hook Migration Guidelines
+1. Deprecated Hook Migration:
+   - Replace useFirebaseQuery with useAllData for better data management
+   - Update component destructuring to match useAllData return type
+   - Ensure proper typing of data fields
+   - Handle null/undefined cases with default values
+   - Update query invalidation to use 'all-data' query key
+
+# Performance Optimization Guidelines
+1. Data Fetching:
+   - Implement granular queries instead of fetching all data at once
+   - Use pagination for large datasets
+   - Cache frequently accessed data
+   - Implement real-time listeners only when necessary
+
+2. State Management:
+   - Use optimistic updates for better UX
+   - Implement proper loading states
+   - Handle errors gracefully with user feedback
+   - Maintain atomic transactions for data consistency
+
+3. Component Optimization:
+   - Memoize expensive computations
+   - Implement virtualization for long lists
+   - Lazy load components and routes
+   - Use proper React hooks dependencies
+
+4. Firebase Best Practices:
+   - Structure data for efficient querying
+   - Minimize unnecessary reads/writes
+   - Use batch operations when possible
+   - Implement proper security rules
+
+5. Code Quality:
+   - Write comprehensive tests
+   - Document complex logic
+   - Follow clean code principles
+   - Use TypeScript for better type safety
+
+6. Error Handling:
+   - Implement retry mechanisms
+   - Provide meaningful error messages
+   - Log errors for debugging
+   - Handle edge cases gracefully
+
+7. UI/UX Considerations:
+   - Show loading states
+   - Provide immediate feedback
+   - Handle offline scenarios
+   - Maintain responsive design
+
+8. Data Validation:
+   - Validate data on both client and server
+   - Implement proper type checking
+   - Handle null/undefined cases
+   - Sanitize user inputs
+
+9. Pagination Implementation:
+   - Use cursor-based pagination for efficiency
+   - Maintain page state in URL
+   - Handle loading states during page transitions
+   - Cache paginated results
+
+10. Modal and Form Handling:
+    - Implement proper form validation
+    - Handle form submission states
+    - Provide clear error messages
+    - Maintain modal state consistency
+
+11. Data Synchronization:
+    - Handle concurrent updates
+    - Implement proper locking mechanisms
+    - Maintain data consistency
+    - Handle offline/online transitions
+
+12. Security Considerations:
+    - Implement proper authentication
+    - Validate user permissions
+    - Sanitize data inputs
+    - Handle sensitive data properly

.env

@@ -0,0 +1,16 @@
+NODE_ENV=development
+VITE_FIREBASE_API_KEY="AIzaSyDaDxYhQdUW3VeN2B-Dd-PbtUh4O-_gTHY"
+VITE_FIREBASE_AUTH_DOMAIN="careops-dev.firebaseapp.com"
+VITE_FIREBASE_PROJECT_ID="careops-dev"
+VITE_FIREBASE_STORAGE_BUCKET="careops-dev.firebasestorage.app"
+VITE_FIREBASE_MESSAGING_SENDER_ID="266860605377"
+VITE_FIREBASE_APP_ID="1:266860605377:web:9d8b0415e495f5e633c940"
+VITE_FIREBASE_MEASUREMENT_ID="G-K18YZ571MX"
+
+# NODE_ENV=production
+# VITE_FIREBASE_API_KEY="AIzaSyCh73Me0Jb0x-5UHHTDgph8VIMtbNIJPXI"
+# VITE_FIREBASE_AUTH_DOMAIN="ehsan-charity-dev.firebaseapp.com"
+# VITE_FIREBASE_PROJECT_ID="ehsan-charity-dev"
+# VITE_FIREBASE_STORAGE_BUCKET="ehsan-charity-dev.appspot.com"
+# VITE_FIREBASE_MESSAGING_SENDER_ID="393202045574"
+# VITE_FIREBASE_APP_ID="1:393202045574:web:915fa20b33356bfd6bb707"

.gitignore

@@ -22,3 +22,9 @@ dist-ssr
 *.njsproj
 *.sln
 *.sw?
+
+# envireonment files
+.env
+.env.production
+
+/coverage

CONTRIBUTING.md

@@ -0,0 +1,54 @@
+# Contributing to CareOps
+
+We love your input! We want to make contributing to CareOps as easy and transparent as possible, whether it's:
+
+- Reporting a bug
+- Discussing the current state of the code
+- Submitting a fix
+- Proposing new features
+- Becoming a maintainer
+
+## We Develop with Github
+We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
+
+## We Use [Github Flow](https://guides.github.com/introduction/flow/index.html)
+Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
+
+1. Fork the repo and create your branch from `main`.
+2. If you've added code that should be tested, add tests.
+3. If you've changed APIs, update the documentation.
+4. Ensure the test suite passes.
+5. Make sure your code lints.
+6. Issue that pull request!
+
+## Any contributions you make will be under the CC BY-NC License
+In short, when you submit code changes, your submissions are understood to be under the same [Creative Commons Attribution-NonCommercial 4.0 International License](LICENSE.md) that covers the project. Feel free to contact the maintainers if that's a concern.
+
+## Report bugs using Github's [issue tracker](https://github.com/yourusername/careops/issues)
+We use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/yourusername/careops/issues/new).
+
+## Write bug reports with detail, background, and sample code
+
+**Great Bug Reports** tend to have:
+
+- A quick summary and/or background
+- Steps to reproduce
+  - Be specific!
+  - Give sample code if you can.
+- What you expected would happen
+- What actually happens
+- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
+
+## Use a Consistent Coding Style
+
+* Use TypeScript for all new code
+* 2 spaces for indentation rather than tabs
+* Use meaningful variable names
+* Write JSDoc comments for functions and complex logic
+* Follow the existing code style
+
+## License
+By contributing, you agree that your contributions will be licensed under the Creative Commons Attribution-NonCommercial 4.0 International License.
+
+## References
+This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md).