AmbaPay/Amba-Admin
production
1eeb19420811f3193e7c1abf681b1639fa358304
success
No local changes to save
HEAD is now at 89193d2 Merge pull request 'feat:added apointment pages' (#8) from main into production
fatal: unable to bind to '/home/amba/.cache/git/credential/socket': Read-only file system warning: unable to unlink '/home/amba/.cache/git/credential/socket': Read-only file system fatal: cache daemon did not start: From https://gitea.yaltopia.com/AmbaPay/Amba-Admin * branch production -> FETCH_HEAD
Your branch is ahead of 'origin/production' by 29 commits. (use "git push" to publish your local commits)
Already on 'production'
Updating 89193d2..1eeb194 Fast-forward src/pages/agents/AgentDetail.tsx | 10 ++++++---- src/pages/agents/Appointments.tsx | 8 ++++++-- src/store/agentStore.ts | 8 ++++++-- src/store/appointmentsStore.ts | 8 ++++++-- 4 files changed, 24 insertions(+), 10 deletions(-)
fatal: unable to bind to '/home/amba/.cache/git/credential/socket': Read-only file system warning: unable to unlink '/home/amba/.cache/git/credential/socket': Read-only file system fatal: cache daemon did not start: From https://gitea.yaltopia.com/AmbaPay/Amba-Admin * branch production -> FETCH_HEAD
up to date, audited 423 packages in 1s 63 packages are looking for funding run `npm fund` for details 2 vulnerabilities (1 moderate, 1 high) To address all issues, run: npm audit fix Run `npm audit` for details.
> amba-admin@0.0.0 build > tsc -b && vite build vite v7.2.4 building client environment for production... transforming... ✓ 3070 modules transformed. rendering chunks... computing gzip size... dist/index.html 0.75 kB │ gzip: 0.42 kB dist/assets/index-MQAihJB3.css 68.21 kB │ gzip: 11.89 kB dist/assets/index-Bm_bLkpH.js 10,109.46 kB │ gzip: 2,733.44 kB ✓ built in 17.36s
(!) Some chunks are larger than 500 kB after minification. Consider: - Using dynamic import() to code-split the application - Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks - Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.