Fix null-safety crashes in app.js DOM event bindings

[Copilot]

app.js called .addEventListener() directly on getElementById() results and accessed toast.textContent unconditionally — any missing DOM element would throw a TypeError and halt all remaining script execution.

Changes

• Optional chaining on event listeners — theme-toggle, btn-share, btn-vcard, btn-install, btn-install-bottom now use ?.addEventListener(...) so a missing element is a no-op instead of a crash
• showToast() null guard — added early return if #toast is absent

// Before
document.getElementById('btn-share').addEventListener('click', ...)
document.getElementById('btn-vcard').addEventListener('click', ...)

// After
document.getElementById('btn-share')?.addEventListener('click', ...)
document.getElementById('btn-vcard')?.addEventListener('click', ...)

// Before
const toast = document.getElementById('toast');
toast.textContent = message; // throws if element absent

// After
const toast = document.getElementById('toast');
if (!toast) return;
toast.textContent = message;

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
rag7	Ready	Preview, Comment	Jul 2, 2026 6:06pm